I apologize for not informing the teams about the syntax change in
redeploy command. We will try to keep the wiki site up-to-date. But
keep in mind that commands are now developed by different people, so
it's beyond a one person resposibility. If you are developing new
commands in v3, please pay attention to the following:
* command syntax should be compatible with v2. If command cannot be
compatible, please discuss this at the CCC meeting. See:
http://wiki.glassfish.java.net/Wiki.jsp?page=AdminOrConfigCompatibilityPage
* update wiki site
(
http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminCommands ) if
the command you implemented is available in v3
Since "redeploy <app-nam>" is useful for NB plugin, I will add
<app-name> as a valid operand to redeploy.
So redeploy is still similar to "deploy --force=true" except if the
operand is an app-name it will get the path from domain.xml. redeploy
will also accept the options available in the deploy command (except for
--force).
Jane
Jerome Dochez wrote:
> As far I as remember, there was no redeploy command in v2. During the
> V3 deployment we reserve all the rights to modify the commands syntax
> in order to be mostly compatible and provide a unified CLI
> experience. so we have changed command options and we will change
> them more until we are a lot closer to FCS and that becomes a final
> interface.
>
> The bug or the broken thing is that the changes do not seem to be
> communicated between the teams so I think Hong and Jane should pay
> extra attention in keeping the page at
> http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminCommands
>
> as up to date as possible for new commands or incompatible changes
> with V2 commands if we have any. Any command not specified on that
> page and implemented in V3 should be 100% compatible with V2 even if
> some of the features behind it are not ready yet.
>
> Jerome
>
> On Mar 11, 2008, at 9:08 PM, vince kraemer wrote:
>
>> You are right. Broken depends on your perspective.
>>
>> So, the question of, "why did this (the syntax) get changed?"
>> remains unanswered.
>>
>> Can anyone answer that question?
>>
>> In the case of directory deployed web apps, etc... the user has
>> entered the name and the path to deploy the app, right?
>>
>> The domain.xml has the correct path associated with the name and
>> should just use that, if there is no path argument given.
>>
>> I think the new "correct" syntax is actually asking tools and users
>> to reenter data. (I cannot really tell, since I don't see any
>> definitive reference for redeploy through the web admin
>> interface)That seems like it will make mistakes easier to make...
>> not harder...
>>
>> vbk
>>
>> PS: I also noticed that Ludo's original question was not answered
>> directly... "what is the real syntax for redeploy or a dir deployed
>> app?" (which I think is really... what is the real syntax for
>> redeploy of a dir deployed app?)
>>
>> Jane Young wrote:
>>
>>> Hi Vince,
>>>
>>> It's not broken... the syntax has changed for redeploy :-)
>>>
>>> Jane
>>>
>>>
>>> Vince Kraemer wrote:
>>>
>>>> It seems like a bad idea to break something that has been working...
>>>>
>>>> Why did this get changed?
>>>>
>>>> vbk
>>>> Jane Young wrote:
>>>>
>>>>> Hi Ludo,
>>>>>
>>>>> The correct syntax for redeply is to use the full path.
>>>>> "redeploy" is the same as "deploy --force=true <path>".
>>>>>
>>>>> Jane
>>>>>
>>>>> Ludovic Champenois wrote:
>>>>>
>>>>>> so what is the real syntax for redeploy or a dir deployed app?
>>>>>>
>>>>>> With TP1, this used to work:
>>>>>>
>>>>>> http://localhost:8080/__asadmin/redeploy?name=WebApplication18
>>>>>>
>>>>>> Since the name 'WebApplication18' is known and it's location is
>>>>>> known (see the list-application), then this command should work
>>>>>> for dir deployed app, no?
>>>>>> Should I do instead:
>>>>>>
>>>>>> http://localhost:8080/__asadmin/redeploy?path=FULLPATH
>>>>>> ?
>>>>>> Ludo
>>>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>