Define the meaning of "hot deployment". Then check if WildFly supports it. If WildFly doesn't support it, wildfly-maven-plugin won't either.
It was hard deployment and not hot deployment as it was a mistake in my original question. Wildfly supports hot deployment. I was looking for a stuff similar to jboss:hard-deploy provided by jboss-maven-plugin in wildfly-maven-plugin but could achieve using maven-antrun-plugin. Thanks.
hard-deploy simple copy the file to the server's deploy directory.
As the WildFly plugin use the management interface, as this is the prefered method and work for standalone and domain mode, there is no hard-deploy.
By default the plugin use the default management connection localhost:9999 and does not know where the server is in the filesystem.
Many thanks for the response .. Wolf-Dieter Fink. Application was running earlier in JBoss 6 AS and it was availing hot deployment feature of it using jboss:hard-deploy. I am trying to implement the same feature by copying exploded EAR file in standalone/deployments folder of Wildfly AS and adding auto-deploy-exploded attribute of deployment scanner of standalone-full-ha.xml to true.
By this way, I believe hard deploy can be achieved in Wildfly AS.
Just a minor correction port 9990 for WildFly by default
James R. Perkins
1 of 1 people found this helpful
Yes, you might use this configuration in standalone mode.
But consider in contrast to AS6 each change to the exploded directory will force a re-deploy.
A better option is to keep the default and deploy the exploded deployments by adding the deployers status files named <your app>.dodeploy or .deployed (see documentation for more details)
Many thanks.. Wolf-Dieter Fink. I have the EAR exploded in standalone/deployments folder and.dodeploy gets created during deployment and .deployed gets generated after deployment after starting the Wildfly.