SONARQUBE C++ community plugin 9.0 and lower unavailable - c++

It is known that in "C++ community plugin" version 0.91 onward,
Configuration setting sonar.cxx.cppncss.reportPath is no longer supported.
So i will have to downgrade the plugin lower than 0.9, and i'm not finding in official sonarqube site or any source code.
Do anybody has the Sonar C++ community plugin of any older version lesser than 0.9? please help and share the link.

Older releases are available in maven repository:
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.codehaus.sonar-plugins%22%20AND%20a%3A%22sonar-cxx-plugin%22
Download:
0.2 - http://repo1.maven.apache.org/maven2/org/codehaus/sonar-plugins/sonar-cxx-plugin/0.2/sonar-cxx-plugin-0.2.jar
0.1 - http://repo1.maven.apache.org/maven2/org/codehaus/sonar-plugins/sonar-cxx-plugin/0.1/sonar-cxx-plugin-0.1.jar

Related

How do I get VS 2017 to install the dependencies for packages that I am trying to install?

I was following a Lynda tutorial that was showing how to add versioning to my APIs. It told me to install the NuGet package Microsoft.AspNetCore.Mvc.Versioning. I tried that and it gave me an error because it needed Microsoft.AspNetCore.Mvc.Core. So I tried to install that package, and, again, another error because it needed another package.
So I started googling for a way to make VS 2017 pull in dependencies with NuGet installation. None of the answers that I found were helpful. I’ve tried managing as packageReference and packages.config. “Allow format selection on first package install” is unchecked. And so on.
So I decided to just power through and add all the dependencies manually. I had to install 29 packages. It took me over half an hour, not including time spent chasing the cat up and down the stairs screaming at the top of my lungs.
Is there some switch I forgot to flip, or some options I didn't add, or does Microsoft really think we might want the option to install a package without installing its dependencies?
How do I get VS 2017 to install the dependencies for packages that I am trying to install?
I have reproduced this issue on my side. This is the correct behavior for nuget. That because the package which you want to install have a indirect dependency Microsoft.AspNetCore.Authentication.Abstractions (>= 2.2.0).
Note: (Version need >= 2.2.0).
However, the default package for the .net core API project also have same indirect dependency Microsoft.AspNetCore.Authentication.Abstractions (>= 2.1.1 && < 2.2.0) with version limit (>= 2.1.1 && < 2.2.0).
Note: version limit (>= 2.1.1 && < 2.2.0).
It conflict with dependency of package Microsoft.AspNetCore.Mvc.Versioning. That the reason why nuget not install the dependencies for package.
To resolve this issue, we just need to update the target framework (Right click project->Properties->Target Framework) from .NET Core 2.1 to .NET Core 2.2 for your .net core API project.
If you do not have the version 2.2.0, please download it from here and install it:
.NET SDKs for Visual Studio
After update the target framework to 2.2, the default package Microsoft.AspNetCore.App will be update to Microsoft.AspNetCore.App 2.2.0, which dependency update to Microsoft.AspNetCore.Authentication.Abstractions(>= 2.2.0 && < 2.3.0). So it compatible with the dependencies of the package Microsoft.AspNetCore.Mvc.Versioning 3.1.1.
Now I can install the package Microsoft.AspNetCore.Mvc.Versioning 3.1.1 with its dependency.
Hope this helps.

Using HtmlAgilityPack NuGet package in dotnet core v1.0

I am trying to use HtmlAgilityPack nuget package in netcoreapp1.0 (I am restricted to this version since AWS Lambda supports only it). Which version of the HtmlAgilityPack package should I use? The point is .NETStandardLibrary 1.6.0 is only compatible with netcoreapp1.0 but I don't see any version of HtmlAgilityPack which would be compatible with .NETStandardLibrary 1.6.0. The minimum version I can see is .NETStandardLibrary 1.6.1 but this is for netcoreapp1.1.
From a .NET Standard API prospective nothing changed between NETStandard.Library 1.6.1 and 1.6.0. We only bumped the version of the meta-package so that we could pull in newer versions of the dependent packages which contain implementation fixes but no real new API surface for NS1.6.
See the issue #171 in DotNet standard repo What's the change in NetStandard.Library 1.6.1 vs 1.6.0?
Even if there will be no HtmlAgilityPack compatible (or build against) netstandard1.6, but there is a netstandard1.6.1 I would just build it for myself by replacing netstandard v1.6.1 nuget package with netstandard v1.6 package ( HtmlAgilityPack is open source - right :) ).
Most importantly there is no netstandard1.6.1, it was never released or even worked on, v1.6.1 stands only for the version of NETStandard.Library NuGet package.

Jython 3 stable version

What is the latest stable version of Jython? I prefer a new version hopefully v3.x
Is it still recommended to use Jython 2.7.0 Final Released (May 2015)
What is Jython 3 sandbox? Is this a official/recommended one?
In Wikipedia it says about v.2.7.1 released in July 2017. Where can I download this version? (if this is the recommended latest one)
Use this link to download the 2.7.1 version:
You should definitely NOT use the newcomers which aren't stable for production purposes. You can follow guys from their dev team for all info regarding releases.

Package X is not compatible with netstandard2.0

I created a .NET Standard v2.0 project in Visual Studio 2017 v15.3.1 and I'm unable to install "Microsoft.EntityFrameworkCore 2.0.0" package in it (by Nuget 4.3). Previously the .NET SDK and Runtime, both 2.0.0, were installed.
The errors I get follow this pattern:
"Package X is not compatible with netstandard2.0 (.NETStandard,Version=v2.0)." (i.e. System.Reflection.TypeExtensions 4.1.0).
What could it be causing these errors?
EDIT: I'll show the exact warnings and errors with an example (there are too many).
Restoring packages for [.csproj path]...
Warning:
Package "System.Collections 4.3.0" was restored using ".NETFramework,Version=v4.6.1" the project target framework ".NETStandard,Version=v2.0". This may cause compatibility problems.
...
Error:
Package Remotion.Linq 2.1.1 is not compatible with netstandard2.0 (.NETStandard,Version=v2.0). Package Remotion.Linq 2.1.1 supports:
net35 (.NETFramework,Version=v3.5)
net40 (.NETFramework,Version=v4.0)
net45 (.NETFramework,Version=v4.5)
netstandard1.0 (.NETStandard,Version=v1.0)
portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
...
Error restoring package. Reverting package changes for 'ClassLibrary1'.
Time elapsed: 00:00:02.4689637
========== Ended ==========
Clicking the "Clear all Nuget Caches" will resolve issue.
Issue solved installing, independently, newer versions for each of the packages' dependencies which were showing error, so that the big package "Microsoft.EntityFrameworkCore 2.0.0" gets installed at last.
Hope it helps.
Edited: It happened to me another time and tried a faster solution. The key was deleting Nuget's cache from the packages' manager configuration.

Is there a way to get ColdFusion Builder 3 to run using Java 8?

I am using Mac OS X El Capitan, with Java(TM) SE Runtime Environment (build 1.8.0_65-b17). ColdFusion Builder 3 uses java runtime 1.6.
Is there a way to install CF Builder, but using the current JDK on my machine?
Too long for comments
I am running Windows but my version of ColdFusion Builder 3 is running Java 8 already. I did not make any changes for this.
When I click on Help > Product Details > Installation Details > Configuration (tab) this is what it reports. I am only including some of the java* information under system properties here:
java.home=C:\Program Files\Adobe\ColdFusionBuilder3\jre
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.8.0_25-b18
java.specification.name=Java Platform API Specification
java.specification.vendor=Oracle Corporation
java.specification.version=1.8
java.vendor=Oracle Corporation
java.vendor.url=http://java.oracle.com/
java.vendor.url.bug=http://bugreport.sun.com/bugreport/
java.version=1.8.0_25
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Oracle Corporation
java.vm.specification.version=1.8
java.vm.vendor=Oracle Corporation
java.vm.version=25.25-b02
I do have update 65 installed on my machine but Builder is using it's own JRE as noted above.
I asked a similar question (Install ColdFusion Builder 2 Update 1 Plug-in in Eclipse 4.3) for installing CFB 2x as an Eclipse plug-in. It seems that the requirements are fairly strict when it comes to CFB.
Here are the install specifications for CFB 3x on the Adobe site:
http://www.adobe.com/products/coldfusion-builder/tech-specs.html
It looks like this version is stuck with Java 1.7 or Eclipse 4.3.2.
Update: I was able to install Eclipse 4.3.2 (Kepler) with 64-bit JDK 1.7u80. I had to add the following to the eclipse.ini file:
-vm
D:/Program Files/Java/jre7/bin
The location of your JDK/JRE may be different.
Further Update: I was able to set up Eclipse 4.3.2 (Kepler) to use the latest 1.8u66 JDK. I modified eclipse.ini after I installed this JDK:
-vm
D:\Program Files\Java\jre1.8.0_66\bin
Eclipse Help > About Eclipse > Installation Details > Configuration has:
-vm
D:\Program Files\Java\jre1.8.0_66\bin\server\jvm.dll
So it looks like it is working with the latest 1.8.
No, it will specifically request Java 1.6 even if you edit the proper plist file (/Applications/ColdFusionBuilder3/CFBuilder.app/Contents/Info.plist). You can get Java 1.6 here https://support.apple.com/kb/DL1572?locale=en_US
You just need to find the eclipse.ini file located beside the eclipse program (or Builder as it were). In there it will have the path to the JDK. Change the path to the JDK on your system.