[
https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16214:
----------------------------------------
I think you need to investigate about which jars does Sonar use to generate the jacoco
reports. The best value is to use the classpath computed by Maven (which are the actual
jars used by the tests), but it's possible that Sonar simply uses the jars of the
modules in target/. If it is so, this can probably be a bug to report directly to Sonar.
Code Coverage jobs needs to have locally available measured plugins
-------------------------------------------------------------------
Key: JBIDE-16214
URL:
https://issues.jboss.org/browse/JBIDE-16214
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.1.1.CR1
Reporter: Vlado Pakan
Assignee: Mickael Istria
Fix For: 4.1.x
Code Coverage calculating via maven build returns 0% coverage because it's using
source code and binary plugins installed from update site.
When these are built locally prior to build calculating code coverage it returns correct
results.
Unfortunately sometimes maven build used plugins installed from update site instead of
those which are locally build.
We need to find way how to fix this.
It's already reported here
https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira