[
https://issues.jboss.org/browse/JBIDE-16099?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-16099:
---------------------------------------
I'm not fully following what this is fixing.
If arquillian is ignoring maven projects how could anything ever work ?
The Arquillian classloader was ignoring maven projects in the workspace. The validator has
worked properly if a project didn't have any dependencies to a maven project in the
workspace.
Got some details on how to test/assert this without having to load
the full wildfly testsuite ?
There is the
https://github.com/jbosstools/jbosstools-arquillian/blob/master/tests/org...
test that tests this issue.
You can manually import
https://github.com/jbosstools/jbosstools-arquillian/blob/master/tests/org...
and
https://github.com/jbosstools/jbosstools-arquillian/blob/master/tests/org...
to test the issue.
BTW
The PR has been applied to the master.
Archives can't be created for Wildfly integration tests
-------------------------------------------------------
Key: JBIDE-16099
URL:
https://issues.jboss.org/browse/JBIDE-16099
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.1.Alpha2
Reporter: Snjezana Peco
Assignee: Snjezana Peco
The Arquillian validator can't analyze some projects (Wildfly integration tests, for
instance). I suppose such projects require some server at runtime.
--
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