On 06/08/2011 07:24 AM, Alexey Loubyansky wrote:
BTW, the CLI uses "deploy --force" to force redeploy.
In that case maybe we should change from strict to force and default it
to true. That way all the terminology remains the same.
On 06/06/2011 04:22 PM, James Perkins wrote:
> On 06/06/2011 03:09 AM, Pete Muir wrote:
>> 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:
>>
> I like the strict option. I think I'll go with that. Seems to make the
> most sense and could loosen up other options in the future if needed too.
>
> So in the end we'll end up with 3 goals; deploy, redeploy and undeploy.
>
> Thanks for the help all.
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
James R. Perkins
JBoss by Red Hat