[
https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-16214:
-------------------------------------
I think it's not problem of Sonar. jacoco.exec file is generated without links to
class/jar files because they are installed from update site not from local file system.
Probably because of pack200 once it was disabled everything works in past. But it's
just my guess.
Sonar is not using jar files from target directory or is not able to link them with data
in jacoco.exec. Those files are available and when build is forced to use locally built
artfacts Sonar analyze is correct. I don't think Sonar can use the same classpath as
maven build uses as far as I can say tycho is building classpath for integration tests and
I don't think Sonar has functionality to build the same path as tycho do
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