[
https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16214:
----------------------------------------
{quote}Unfortunately sometimes maven build used plugins installed from update site instead
of those which are locally build.{quote}
[~vpakan] I've given another thought on this topic, and I think that thanks to changes
done as part of JBIDE-16309 , builds should not see jars that may come from another
nightly site. So it's most likely that since jobs can now only see jars that are in
the same reactor or in local maven repo, this issue got fixed magically.
Can you please check it?
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 was sent by Atlassian JIRA
(v6.2.3#6260)