Hmmm. I must not be reading those.
In V2, we don't have an *asadmin redeploy* command and no
user has reported this to be a flaw. Why would we want users
to undergo deploy/redeploy/undeploy when deploy/undeploy worked?
Again, I am talking only w.r.t. "asadmin".
Jerome Dochez wrote:
> Independently of the --force fate, I think a redeploy command is highly
> desirable as it comes quite naturally to Java EE users accustomed to
> deploy/redeploy/undeploy actions as specified everywhere in industry
> standard docs, books and postings.
>
> Jerome
>
> On Mar 13, 2008, at 9:41 AM, Kedar Mhaswade wrote:
>
>> I thought that the plan of record is till we find the correct default
>> value
>> for --force, it remains true. This was after ccc meeting yesterday.
>>
>> Thus, asadmin deploy foo.war [foodir] followed by asadmin deploy foo.war
>> [foodir] should result in redeployment of the underlying
>> application/module.
>>
>> This means, we should not use "redeploy" command just yet, as "deploy
>> over deploy" is supposed to achieve the same effect.
>>
>> I am not convinced we ought to have a "redeploy" command.
>>
>> Jerome, Bill, please help clarify doubts here.
>>
>> - Kedar
>>
>> Vince Kraemer wrote:
>>> This is good news. I am happy that this useful command is getting a
>>> second chance.... for users sake.
>>> The v3 plugin code could be changed to work with just about
>>> anything. It isn't pleasant, but it is do-able.
>>> Forcing users to go back to a poorer interface, after a better one
>>> has been identified and implemented, is.... more than unpleasant.
>>> vbk
>>> Hong Zhang wrote:
>>>> Hi, Vince
>>>>
>>>>> I disagree with your analysis.
>>>>>
>>>>> I think that whether by luck or deep analysis, Jerome made the
>>>>> right decisions concerning the need for a redeploy "command".
>>>>>
>>>>> Eliminating it for 'ease of maintenance' is not a compelling
>>>>> justification.... especially when there was a working
>>>>> implementation that was in-place....
>>>>
>>>> When we made the decision, we were not aware of that the NetBeans
>>>> plug in was using the new redeploy command. And I guess we did not
>>>> realize the parameter differences of the new redeploy command vs the
>>>> old "deploy --force". In any case, we will restore the old syntax
>>>> of redeploy command and the changes should be checked in soon.
>>>>
>>>> - Hong
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>