[
https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16214:
----------------------------------------
This kind of exception happens when multiple jars provide a class. Ideally, this should
never happen. Can you please describe which component should I use (common I guess) and
which mvn command you did run to get it. I'll check whether this is a scirpt issue of
a jar issue.
But anyways we need code coverage report generated by jacoco jenkins
plugins
Do you use this jacoco jenkins plugin? In the
jenkins.eng.mw.redhat.com instance, we
don't use the plugin. Instead we rely on the script to create HTML reports and link
them.
Do you use Sonar for coverage as well?
There are many ways to consume coverage report, and I don't think it's necessary
to keep all of them (too much work, no added-value). Which one(s) do you actually use
currently? I'll make efforts on those.
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