Community
Participate
Working Groups
To determine that it fixes the problems with running selected tests on Java 7. http://sourceforge.net/projects/eclemma/files/07_JaCoCo/trunk/jacoco-0.5.5.201111252057.zip/download
If it fixes them. I'll open a CQ so we can consume the libraries in Juno.
I tested this and it works. Marc, is there any functionality that we need in 0.5.6 or should 0.5.5 be sufficient? If not, I'll open a the CQs for 0.5.5.
I don't think there is any Eclipse specific enhancement or bug fix in 0.5.6. The important issues are Maven related. Here is the complete change log: http://www.eclemma.org/jacoco/trunk/doc/changes.html
The CQ is here https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5990
Okay, I talked to Barb today and apparently I did the original CQ wrong. I opened new CQs today ant jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5998 agent jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5999 org.jacoco.agent jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6000 org.jacoco.ant jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6001 org.jacoco.core jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6002 org.jacoco.agent jar https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6003
Made a mistake, should have been https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6006 for org.eclipse.jacoco.report
Marc, can you point us to the location where we can download jars with source? The ones I downloaded and included on the ipzilla requests for the Eclipse foundation legal team only include class files which is unexpected. We need the source as well so they can scan the source and approve it for our use.
Unfortunately we don't create source bundles (yet). But the corresponding Subversion tag is this url: https://eclemma.svn.sourceforge.net/svnroot/eclemma/jacoco/tags/v0.5.6 The source tree can be downloaded as tar.gz here: http://eclemma.svn.sourceforge.net/viewvc/eclemma/jacoco/tags/v0.5.6/?view=tar
Marc, thanks for the link to the source. The IP team has reviewed it. They have a question regarding the agent jar. They state that "the agent attachment appears to include more class files than the source provides for agent.rt." https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5999#c10 Do you have any insight into this issue?
Kim, this is correct. The agent JAR is somehow special: It is a resource that needs to be provided for the JVM under test. It must contain all required class files, which are (using the Maven shade plugin) collected from: * org.jacoco.core * org.jacoco.agent.rt * org.objectweb.asm Also classes in the JAR get renamed to the package prefix "org.jacoco.agent_<randomid>" during packaging to avoid any name clashes with the application under test. BTW, the packaging of the agent JAR has not changed since the very first release 0.1.0 in 2009.
The new jacoco jars have been approved via parallel IP and I've released them to the org.eclipse.test bundle in the repo. I've renabled JaCoco to run on the windows machine during integration builds.
*** Bug 342715 has been marked as a duplicate of this bug. ***
