[ http://jira.codehaus.org/browse/MJBOSS-6?page=all ]
Jeff Genender closed MJBOSS-6:
------------------------------
Resolution: Fixed
Fix Version: 1.3.2
Great idea. I have been doing the undeploy/deply thing myself and never
thought about using the redeploy method.
I went the jboss:redploy route.
Sending pom.xml
Sending src/main/java/org/codehaus/mojo/jboss/AbstractDeployerMojo.java
Sending src/main/java/org/codehaus/mojo/jboss/ConfigureJBossMojo.java
Sending src/main/java/org/codehaus/mojo/jboss/DeployMojo.java
Adding src/main/java/org/codehaus/mojo/jboss/ReDeployMojo.java
Sending src/main/java/org/codehaus/mojo/jboss/UndeployMojo.java
Transmitting file data ......
Committed revision 1857.
Its in the 1.3.2-SNAPSHOT.
> Provide support for JMX redeploy
> --------------------------------
>
> Key: MJBOSS-6
> URL: http://jira.codehaus.org/browse/MJBOSS-6
> Project: Maven 2.x JBoss Plugin
> Type: Improvement
> Environment: JBoss 4.0.3SP1
> Reporter: Daniel J. Bernstein
> Fix For: 1.3.2
>
>
> JBoss is not re-deploying using the default JMX URL because the method
> "deploy" does nothing when the EAR has already been deployed. It would be
> very useful, ** especially for continuous integration **, to provide a
> "redeploy" goal. The redeploy goal would be exactly the same as the "deploy"
> goal, except it would use the JMX "redeploy" methodName in the URL. The new
> URL would be:
> /jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=redeploy&argType=java.net.URL&arg0=
> Or perhaps it could even be a flag on the "deploy" goal.
> <configuration>
> <redeploy>true</redeploy>
> ...
> </configuration>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
