Any ideas when cobertura will support java 7?
Found http://sourceforge.net/tracker/index.php?func=detail&aid=3295711&group_id=130558&atid=720018
We preferred cobertura over emma and other code coverage tools and looks like we have to redo all those again, now that none of them support java 7 yet.
Thanks
Cobertura 2.0.3 supports Java 7, the cobertura-maven-plugin version 2.6 which uses this version has been just released
I was able to get it to work by adding the following argument:
-XX:-UseSplitVerifier
I got it from here.
I think the answer is: it won't. There is discussion on the mailing list that the project is not being maintained, and there are Java 7 bugs that have been open for a year. On the bright side, JaCoCo functionality is comparable and is being actively maintained.
Further to Jagger's comment, it looks like this is now being actively worked on for the next release - see:
https://github.com/cobertura/cobertura/commit/b303fdc94851088a3c8699651770faef33180924
with the comment "Fix java 7 stack map issue".
Old thread, but my answer may be useful: Cobertura does support the latest Java versions and is actively maintained. eCobertura (the Eclipse plug-in for Cobertura) hasn't been maintained since 2010, but Cobertura itself is still maintained.
eCobertura will not run with Java 7 or higher, but Cobertura will.
If you are looking for coverage reports (suc h as the ones that eCobertura used to provide), just run the Cobertura maven plugin with mvn cobertura:cobertura and check the HTML report under target/site/cobertura/index.html
Related
Similar to EclEmma which is a plugin on eclipse, is there any plugin for jdeveloper to see run junit tests and see the code coverage? I see EMMA integration plugin in jdeveloper but after installing wasn't able to see any difference and also could not get any documentation on what the plugin is supposed to do.. Please help!
I know it is an old question but just in case someone came across it.
There is a blog post here explaining how to get Emma work with your JDeveloper. I also tested this on my latest JDeveloper 12c and it works fine.
Also regarding the documentation and how to use Emma it is all listed in their site here
I took a look on the Clirr Plugin (http://docs.sonarqube.org/display/PLUG/Clirr+Plugin). However, according to
Any alternatives to Clirr (binary and source compatibility with older releases)? , clirr is rather dated.
Are any of the alternatives compatible to clirr?
best,
Roman
Sorry, there's no SonarQube plugin for a tool that's less dated than Clirr.
I want to use Spark-Java 2.0 with Jetty 9.2. The trick here is that the Maven repository for Spark has dependency on jetty 9.0. The reason is that we already have working code using 9.2. When we bind/load the Spark jar at runtime there are class load errors.
The question is what issues may arise for Spark if I do a build to use jetty 9.2?
They other question could be, can I use excludes some how to load Jetty 9.2 over the 'requested' 9.0 classes? Is that possible, or will it cause me more bother?
Let me know if you think of other considerations. Also let me know where to find release notes for Jetty if you can? I looked for Jetty release notes here: Jetty Documentation hub; it is a little disappointing because they simply link to updated manuals. I look for Release Notes to show me what's different and changed between versions -- A new manual won't help unless I have a way to do 'diff' on the two manuals.
My thinking is that a jump between 9.0 to 9.2 should be a valid increment. My thanks in advance for your insights.
My understanding is that Findbugs 3.0.0 will support analyzing Java 8 bytecode. I see that there is a beta version of it available here:
http://sourceforge.net/projects/findbugs/files/findbugs/3.0.0/
SonarQube is waiting until the final version of Findbugs 3.0.0 is released before upgrading their Java plugin to use it. This means SonarQube is unable to analyze our Java 8 projects.
Is there a target date for Findbugs 3.0.0 release or a known workaround for using the beta version of it with SonarQube?
Well, 3.0.0 RC1 is released today (25.06.2014) and we plan to release 3.0.0 final (if there will be no major regressions reported) in July.
Update: 3.0.0 is released on 06.07.2014, see https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-July/004029.html
As per mailing list thread : https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-May/003999.html
The release is now mainly depending on early adopters feedback.
I've used the C plugin for Sonar for while.
But the plugin library list has recently been updated and seems to indicated the C plugin has been merged with the commercial c++ plugin?
Does that mean that the C plugin is no longer free of charge?
Is the C plugin still active, in terms of developing features and support?
Jesper
The C plugin is still available for download and usage.
But it will no longer be supported and will no longer evolve.
The default C/C++/Objective-C plugin for SonarQube is commercial right now. You have to pay to use it. The Sonar Community C /C++ plugin is good. It has many functionalities. Its called sonar-cxx. You can find it Here- https://github.com/wenns/sonar-cxx/wiki/Installation
You can download it from here - https://github.com/wenns/sonar-cxx/releases/tag/cxx-0.9.1