search

jbossas / jboss-as-maven-plugin

Maven plugin to deploy applications to JBoss AS 7 (moved to https://github.com/wildfly/wildfly-maven-plugin)
74 stars 69 forks source link

Allow jboss-as:redeploy not to fail when there's no deployment of that name #63

Closed OndraZizka closed 9 years ago

OndraZizka commented 10 years ago

In most scenarios, the user doesn't care if the app is or is not there. He just wants to have an app deployed.

Having to keep in mind whether to use :deploy or :redeploy is quite unpleasant.

Adding a parameter "force" to :redeploy would help.

:deploy already has "force" but AFAIK that doesn't overdeploy the app, just doesn't fail and keeps the old one. Or at least that's how it sounds from the docs:

"If force mode is disabled, the deploy goal will cause a build failure if the application being deployed already exists." http://docs.jboss.org/jbossas/7/plugins/maven/latest/deploy-mojo.html

OndraZizka commented 10 years ago

Hmm, just tried mvn "jboss-as:deploy" and it seems that it redeploys too - EAP 6.1 did stop, redeploy, start the app. Interesting. Not documented.

OndraZizka commented 10 years ago

Ah, so it just stopped and started, but the app remained the same. So :deploy didn't fail although it should.

jamezp commented 10 years ago

Using deploy on an already deployed application should result in a redeploy unless the force property is set to false. If the deployed application didn't change, that is an issue though.

OndraZizka commented 10 years ago

Yes, that's what happened. The app remained the same. Even after undeploying and deploying (and I checked that the app is gone in the CLI).

After I deleted the temporary files from EAP, it started working again. Seems like EAP bug. I will try with latest EAP and WildFly.

jamezp commented 9 years ago

Cleaning up issues and I think this should be solved.