Hong Zhang wrote on 10/15/09 6:18 PM:
> Hi, Bill
>
>> A few of us have been discussing some issues with deployment recently and
>> I'd like to let everyone know what we ended up with and get your
>> feedback.
>>
>> We have three ways to deploy an application using the command line and
>> two cases to consider for each operation.
>>
>> Here's what we came up with:
>>
>> | foo does not exist | foo exists
>> ------------------------------------------------------------
>> deploy foo.war | + | X
>> deploy --force foo.war | + | + [2]
>> redeploy foo.war | + [1] | +
>>
> Today's behavior for "redeploy foo.war" is we would fail redeployment
> when "foo does not exist". If we are not going to make any of the
> changes for [1], this row should remain like this?
>
> redeploy foo.war | X | +
Hmmm... Someone told me that wasn't true, but if you're sure that's
the current behavior then I think we leave it alone.
> Also today's behavior for "deploy foo.war" when "foo exists" is we would
> resolve the name conflict and assign a new name, so we have decided we
> would fail that case? I agree failing would be more user friendly, I
> implemented the resolving name part only because I thought that was the
> spec requirement. If by having the --name option already satisfies the
> spec requirement, I will be happy to make this change. :-)
Yes, make that change.