[ https://issues.jboss.org/browse/JBASMP-70?page=com.atlassian.jira.plugin.... ] Amal Jose updated JBASMP-70: ---------------------------- Description: 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 was: 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) -- This message was sent by Atlassian JIRA (v6.2.6#6264)