geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2814) Add a second repository to Geronimo
Date Thu, 08 Feb 2007 21:48:05 GMT


Ted Kirby updated GERONIMO-2814:

    Attachment: repo2-111-plan.xml

Here is a 1.1 plan for a second repo.

Here are 1.1 usage instructions:

1. Deploy it via 
deploy repo2.xml

2. The Repo2.root attribute gives the directory of the 2nd repo. It can be an absolute path,
or relative to GERONIMO_HOME.
My example is relative, so create the directory:
mkdir <geronimo_home>/repo2

3. Use the deploy list-targets command to see your old and new repos:
C:\wasce110x\bin>java deployer.jar list-targets
Available Targets:

4. I set each in a variable, ie
set REPO2=example/myrepo/1.1.1/car?ServiceModule=example/myrepo/1.1.1/car,j2eeType=ConfigurationStore,name=Local2

5. deploy an app to the new repo:
deploy --targets %REPO2% myapp.war

6. The deploy list-modules output is now cluttered with those long target names.
list-modules %REPO2% gives the accustomed short output.

7. It looks like deploy and undeploy without targets will put the app in all repos, and take
it out of all of them.
To remove an app from a specific repo:
undeploy "%REPO2%|geronimo/jsp-examples/1.1.1/war"
The syntax is target|module. The | character is a bad choice, since it is command pipe indicator.
Hence, I enclosed it in "".

I was running into some problems with this undeploy, so I recommend using --targets on deploy,
to keep it simple...

> Add a second repository to Geronimo
> -----------------------------------
>                 Key: GERONIMO-2814
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1.x, 2.0-M2
>            Reporter: Ted Kirby
>            Priority: Minor
>             Fix For: 1.1.x, 2.0-M2
>         Attachments: repo2-111-plan.xml, repo2-ag20-plan.xml
> It would be nice to allow for a second repository for applications separate from the
default repository used by geronimo.
> One use case would be for multiple server instances where the geronimo repository would
be read-only, and each server instance would have its own read-write repository.
> I have attached a 2.0 plan for a second repository, called repo2.xml.
> Here is how to use it:
> mkdir <germonimo_home>/repo2
> deploy repo2.xml
> The target names are long and cumbersome:
> >java deployer.jar list-targets
> Available Targets:
>   org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2
>   org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local
> Use of environment variables recommended for command-line use.
> To deploy to the new repo, use:
> deploy --targets %REPO2% sample.war
> deploy list-modules also gives those long target names on each module.
> However, deploy list-modules %REPO2% gives the accustomed short output.
> >java deployer.jar undeploy  "%REPO2%|geronimo/jsp-examples/1.1.1/war"

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message