5:06 a.m.
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: http://www.atlassian.com/software/jira
5:10 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
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: http://www.atlassian.com/software/jira
8:21 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3215:
----------------------------------
Priority: Minor (was: Major)
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
Priority: Minor
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: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3215:
---------------------------------------
A simplified way of running the testsuite now is:
mvn -Djboss710.home=path-to-as710 integration-test
otherwise if you have jbossXYZ.home defined in settings.xml, you can still do
mvn -Pjboss710 integration-tests
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
Priority: Minor
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: http://www.atlassian.com/software/jira
3:19 a.m.
New subject: [JBoss JIRA] Reopened: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano reopened JBWS-3215:
-----------------------------------
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
Priority: Minor
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: http://www.atlassian.com/software/jira
5:16 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on JBWS-3215 at 9/8/11 5:15 AM:
---------------------------------------------------------------
The testsuite profile is automatically enabled unless the -Dno-testsuite prop is provided.
That's the case when deploying through ant build and/or building src/bin distro. That
is also to be used when doing mvn install / deploy for avoiding running the full
integration testsuites.
was (Author: asoldano):
The jbossXYZ profiles are now also automatically enabled by the presence of
-DjbossXYZ.home props.
The testsuite profile is automatically enabled unless the -Dno-testsuite prop is provided.
That's the case when deploying through ant build and/or building src/bin distro. That
is also to be used when doing mvn install / deploy for avoiding running the full
integration testsuites.
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
Priority: Minor
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: http://www.atlassian.com/software/jira
5:16 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on JBWS-3215 at 9/8/11 5:16 AM:
---------------------------------------------------------------
A simplified way of running the testsuite now is:
mvn -Pjboss710 -Djboss710.home=path-to-as710 integration-test
otherwise if you have jbossXYZ.home defined in settings.xml, you can still do
mvn -Pjboss710 integration-tests
was (Author: asoldano):
A simplified way of running the testsuite now is:
mvn -Djboss710.home=path-to-as710 integration-test
otherwise if you have jbossXYZ.home defined in settings.xml, you can still do
mvn -Pjboss710 integration-tests
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
Priority: Minor
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: http://www.atlassian.com/software/jira
5:20 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-3215) Review the way testsuite is run using Maven
[
https://issues.jboss.org/browse/JBWS-3215?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3215:
---------------------------------------
There's still need to provide the jbossXYZ profile because that can't be
automatically derived from the jbossXYZ.home props because multiple of them can be defined
at the same time in settings.xml.
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
Priority: Minor
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: http://www.atlassian.com/software/jira
4611
days inactive
4817
days old
jbossws-issues@lists.jboss.org
7 comments
1 participants
participants (1)
-
Alessio Soldano (JIRA)