[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16214: ---------------------------------------- Ok. I don't know how to have it working for the Jenkins plugin. The script I've written dynamically computes the list of jars to use by reading surefire configuration. This cannot be achieved by the Jenkins plugin, it would require to rewrite another Jenkins plugin. On the Jenkins instance, we have an extra build step running the (currently Ant-based) script that generates HTML report, and we use the Jenkins Link plugin to add a link to the reports. Ok, That's cool. How are Sonar reports behaving? Do they reports accurate metrics? Not sure it will be able to bind classes, and I don't know what we can do with it. A general solution could be that Tycho avoids using the pack200 jars. http://dev.eclipse.org/mhonarc/lists/tycho-user/msg05194.html However, I couldn't get much help on this topic. About the multiple class issue, I'll try to reproduce the scenario you describe and find whether there's something that can be done in the script. But IMO, the solution is more to fix jars to avoid multiple class definition than tweaking the script to workaround this bad practice. -- 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