Another option is add a strict flag to the deploy goal:
e.g.
strict -- default false, if false, the plugin will deploy the application if not already
deployed, otherwise it will attempt a redeploy.
Of course, I'm arguing for false as the default, but we could have true. Either way,
removes the naming problem..
On 6 Jun 2011, at 11:05, Pete Muir wrote:
On 5 Jun 2011, at 01:13, James Perkins wrote:
> Hello All,
> While working on the Maven deployment plugin we've been contemplating what the
goals should be named. Currently we have 4 goals; deploy, deploy-or-redeploy, redeploy and
undeploy.
>
> We kind of feel deploy-or-redeploy will be the default most people would use. It
seems a little verbose for the default. I've thought about making deploy act as the
deploy-or-redeploy,
I'm for making deploy-or-redeploy the "default" - i.e. the deploy goal.
> but I'm a bit concerned that users will assume it will fail if the deployment
already exists.
Something I mean to ask was why users would assume this? Because this is the way deploy
works in the AS7 deployment API?
>
> So my question to the lot of you is how would you interpret these goals and can you
think of some better names? Mainly a replacement for deploy-or-redeploy, but any other
suggestions are welcome.
>
> Currently as a replacement for deploy-or-redeploy we have always-deploy and
force-deploy.
>
> Thanks in advance,
>
> --
> James R. Perkins
> JBoss by Red Hat
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev