![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
1.2 |
|
Assignee:
|
Javier Murciego
|
|
Created:
|
16/Jul/12 1:01 PM
|
|
Description:
|
Mail from Thomas Cherel:
I was looking at defect MWAS-62, skip does not work for ejbdeploy. It actually does not seem to work for a few other goals: wsAdmin, wsStartServer, wsStopServer.
Is it on purpose or is it a defect?
The problem that I am facing is that I am using the WAS plugin to run my integration tests. Some of the WAS actions are triggered during the pre-integration-test phase:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>was6-maven-plugin</artifactId>
<executions>
<execution>
<id>restart-was</id>
<phase>pre-integration-test</phase>
<goals>
<goal>wsStopServer</goal>
<goal>wsStartServer</goal>
</goals>
<configuration>
<!-- If integration tests are skipped, we skip WAS restart -->
<!-- It does not seem to work with the was6-maven-plugin -->
<skip>${skipIntegrationTests}</skip>
</configuration>
</execution>
</executions>
</plugin>
When doing a build (maven clean/install) without running the integration tests, I would like to skip all the websphere related actions.
Thanks in advance for your input.
|
|
Project:
|
Maven 2.x WebSphere 6 Plugin
|
|
Priority:
|
Major
|
|
Reporter:
|
Javier Murciego
|
|
|
|
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
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email