Hi Gianny,
Thanks for checking that. I was expecting to see it under the general
options after I typed deploy.bat to see the usage. Then I was expecting to
see it after I typed " deploy.bat help deploy". I did see the option there
but there is no explanation.
Command-line deployer syntax:
deployer [general options] command [command options]
Help for command: deploy
deployer deploy [--inPlace] [--targets target;target;...] [module]
[plan]
Normally both a module and plan are passed to the deployer.
Sometimes the module contains a plan, or requires no plan, in
which case the plan may be omitted. Sometimes the plan
references a module already deployed in the Geronimo server
environment, in which case a module does not need to be
provided.
If no targets are provided, the module is deployed to all
available targets. Geronimo only provides one target (ever), so
this is primarily useful when using a different driver.
It is best that we make them consistent as I seldom use the distribute
command. The other thing is that I found out the --inPlace option only
accept directory name, and doesn't allow for packed module. It would be
nice to mention this too, if this is true.
Thanks,
Lin
-----Original Message-----
From: Gianny Damour [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 8:47 AM
To: [email protected]
Subject: Re: in-place deployment
Hi Lin,
I just checked and you can do:
$ java -jar bin/deployer.jar help distribute
Command-line deployer syntax:
deployer [general options] command [command options]
Help for command: distribute
deployer distribute [--inPlace] [--targets target;target;...]
[module] [plan]
<...>
If inPlace is provided, the module is not copied to the
configuration store of the selected targets. The targets
directly use the module.
The help for the deploy command identifies the --inPlace flag but does
not provide a description for it.
Thanks,
Gianny
Lin Sun wrote:
>Thanks. I executed deploy.bat but didn't see the -inPlace option from the
>help menu. Should we add this option to the output of executing
deploy.bat?
>
>Then I saw David Jenck's article
>(http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Exposing+W
e
>b+Applications+on+distinct+ports), so I figured out I can just call
>"deploy.bat deploy --inPlace" to use it. What I found out is if I execute:
>
>deploy.bat deploy --inPlace path\hello.war
>
>I got the following error:
> Error: Unable to distribute hello-1.1.war: In place deployment is
> not allowed for packed module
>
>Then I tried:
>deploy.bat deploy --inPlace path\hello
>
>and it worked well. I did see David used an ear file as the last parameter
>in the example given in the article...
>
>Lin
>
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
>Mulder
>Sent: Tuesday, June 13, 2006 2:42 PM
>To: [email protected]
>Subject: Re: RELEASE-NOTES-1.1
>
>On 6/13/06, Lin Sun <[EMAIL PROTECTED]> wrote:
>
>
>>I am trying to learn what the in-place deployment mean and how to use it.
>>My understanding was that users can update the hot deploy files (for
>>example, update one jsp file) in the Geronimo_home\deploy directory and
>>server will redeploy the change automatically. This was not working in
>>1.0, as users need to replace the entire directory in the
>>Geronimo_home\deploy directory.
>>
>>
>
>That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>
>But in 1.1, there is a separate option, which is to not copy your
>files to the hot deploy directory at all, but instead use the deploy
>tool with a special option to enable an in-place deployment. This
>means that instead of copying your files into the server directory at
>all, it will deploy and access them from wherever they currently are.
>
>Thanks,
> Aaron
>
>
>
>>But after reading your note below, I think I am lost. Please advise.
>>
>>Lin
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
>>Mulder
>>Sent: Thursday, June 08, 2006 7:23 PM
>>To: [email protected]
>>Subject: Re: RELEASE-NOTES-1.1
>>
>> - We should add a point about in-place deployment. "Geronimo
>>supports in-place deployment, which means an archive or directory can
>>be deployed without being copied into the Geronimo directory tree."
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
