]
Alessio Soldano commented on JBWS-3215:
---------------------------------------
Of course, the documentation on wiki needs to be fixed as part of this issue resolution.
Review the way testsuite is run using Maven
-------------------------------------------
Key: JBWS-3215
URL:
https://issues.jboss.org/browse/JBWS-3215
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-native, productization
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
Instead of requiring us/users to do what follows to run the testsuite
> mvn -Ptestsuite,jbossXYZ -DjbossXYZ.home=.. test
we should probably be able to support something like:
> mvn -DjbossXYZ.home=.. integration-test
The move of non-unit tests to integration-test phase is being done as part of JBWS-3210,
the rest is probably a matter of implicitly getting the target container from the
jbossXYZ.home defined in the env and removing the testsuite profile / automatically
enabling the testsuite modules, which just have integration tests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: