[
https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18008:
----------------------------------------
The actual problem is that target/classes folder contains no class file and screws up
FindBugs because it compiles it's own class inside a jar. A workaround would be to be
able to tell FindBugs to look in other locations, but since we're having a look at it,
I feel there is an opportunity for simplifying the packaging of this bundle.
Nested jars prevent SonarQube/FindBugs from running
---------------------------------------------------
Key: JBIDE-18008
URL:
https://issues.jboss.org/browse/JBIDE-18008
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: archives
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.2.0.CR1
Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's
classes get included in some nested jar (and get to different location that
target/classes).
Cf
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{code}
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar
(default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute
Findbugs: Findbugs needs sources to be compiled. Please build project before executing
sonar and check the location of compiled classes. -> [Help 1]
{code}
This is an exploded bundles with nested jars, we should investigate whether it's
possible to turn it into a more standard jar, which would still be usable in its Ant
version. Cf
./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest
Also, the jvmmonitor bundles use nested jars. We should avoid that too.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)