]
James Perkins closed JBASMP-70.
-------------------------------
Resolution: Rejected
This isn't going to be done for the {{jboss-as-maven-plugin}}. New features will only
go into the [{{wildfly-maven-plugin}}|https://issues.jboss.org/browse/WFMP/].
Hard deploy is not supported
----------------------------
Key: JBASMP-70
URL:
https://issues.jboss.org/browse/JBASMP-70
Project: JBoss AS Maven Plugins
Issue Type: Feature Request
Reporter: Amal Jose
Priority: Minor
In Jboss 5 days we used to use a different plugin - which supports jboss hard -deploy i.e
it copies the war to location where deployement scaner of jboss is searching a
war...advantage of this particular implementation is that JBOSS need not be up for the
plugin to run - once the jboss is up, it will take up the war..
The current implementation does support soft deploy using JBOSS Management API..but there
is no hard-deploy goal that used to be supported in JBOSS 5 plugins like
http://mojo.codehaus.org/jboss-maven-plugin
Reducing priority as this is possible using other plugins like antrun of maven...
But can JBOSS AS MAVEN plugin support hard deploy (offline Deploy-where jboss instance is
not running)
Some online discussions regarding same :
http://stackoverflow.com/questions/22936893/jboss-7-x-redeploy-option