Community
Participate
Working Groups
What is the rationale behind this?
There are a few reasons: 1) Jacoco has not actually been functional in our builds for many months. The coverage results for M4 and M5 show 0% coverage across all tests, and same with recent integration builds: http://download.eclipse.org/eclipse/downloads/drops/S-3.8M4-201112091447/coverage.php http://download.eclipse.org/eclipse/downloads/drops/S-3.8M5-201201251800/coverage.php 2) Jacoco has been found to be corrupting our class files. See for example bug 342460 and bug 372867. This doesn't seem to be a mature tool yet, which might explain why it is at version 0.5 3) We have no releng resources to focus on improving this in the near term. There are much bigger releng issues we need to sort out first. If things settle down after Juno and there is a volunteer to work on it (and Jacoco is more stable), we can always add it back in the future.
Kim, please fix this asap. It causes random test failures and wastes our time tracking those down.
Is only a change in /org.eclipse.test/library.xml needed?
Commit for org.eclipse.test http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=f0ed6cd00346f67407c19968cbb398e341140255
Created attachment 212548 [details] patch
Running test build to ensure this doesn't break anything.
Test build successful. Released for 3.8M6.
Verified in I20120313-2000.
I also released this change to the R4_2_primary branch of org.eclipse.releng.eclipsebuilder
*** Bug 378421 has been marked as a duplicate of this bug. ***
