[
https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-16214:
-------------------------------------
I use word link in meaning some relation to class/jar file. Thanks for explanation.
I agree with you Sonar is probably using classes/jars from target folder. He is using
pom.xml file so I guess it analyses it and then uses class/jar files dependent on
information stored in pom.xml file. But I was not able to find information confirming it.
But this part of jenkins job log file is suggesting that I could be right about it:
{noformat}
[INFO] [07:30:47.133] Base dir:
/home/jbossqa/workspace/jbosstools-trunk.jsf.bot.tests.codecoverage/modules/jsf/plugins
[INFO] [07:30:47.133] Working dir:
/home/jbossqa/workspace/jbosstools-trunk.jsf.bot.tests.codecoverage/modules/jsf/plugins/target/sonar
[INFO] [07:30:47.133] Binary dirs:
/home/jbossqa/workspace/jbosstools-trunk.jsf.bot.tests.codecoverage/modules/jsf/plugins/target/classes
{noformat}
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