[
https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-16093:
---------------------------------------
The Java Builder fails because the Arquillian validator catches Exception when creating an
archive, but Throwable (java.lang.NoClassDefFoundError, for instance) can also be thrown.
I have fixed the issue. Now, Wildfly projects are built correctly.
The Arquillian validator logs a warning if it can't create an archive.
The Arquillian validator runs only for those projects that have the Arquillian nature.
Before, it ran for any project that had an Arqullian JUnit test. This will improve
performance when importing a big distribution similar to Wildfly, but a user will have to
add the Arquillian nature to a project if he wants to use the Eclipse Arquillian
features.
The Arquillian validator won't run when importing the Wildfly distribution.
The Arquillian validator can't analyze some projects (Wildfly integration tests, for
instance). I suppose such projects require some server at runtime. I have created
JBIDE-16099.
The PRs:
https://github.com/jbosstools/jbosstools-arquillian/pull/36 - master
https://github.com/jbosstools/jbosstools-arquillian/pull/37 - jbosstools-4.1.x
https://github.com/jbosstools/jbosstools-arquillian/pull/38 - jbosstools-4.1.1.x
NPEs when compiling wildfly codebase
------------------------------------
Key: JBIDE-16093
URL:
https://issues.jboss.org/browse/JBIDE-16093
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.1.CR1
Reporter: Andre Dietisheim
Assignee: Snjezana Peco
Priority: Critical
Fix For: 4.1.1.CR1, 4.2.0.Alpha1
Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79
installed and building the wildfly workspace I run into several NPEs caused by
arquillian.
!npes-building-wildfly.png!
!npes-building-wildfly-2.png!
--
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