geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2814) Add a second repository to Geronimo
Date Wed, 04 Jun 2008 03:34:45 GMT


Joe Bohn commented on GERONIMO-2814:

By this last comment I assume you mean a plugin that we would include with our samples?  
I have a sample ready to go if that was the intent.  Or, did you indent for an independent
plugin (like we have for directory).  That seems like overkill to me and would have to go
through an independent vote to release it ... but it would be easy to make it.   There is
also the issue that I needed to create a repository directory as part of the plugin.   I did
this via the plugin-artifact/copy-file but I had to assume some name and location.  I  just
used the same name and location as in the sample.  If this is what you intended then I think
it might also make sense to move the discussion about multiple repositories under samples.
  So the question is "were you thinking of a sample or something else"?  If it was a sample
then I will check in what I have.   

> 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
>            Assignee: Joe Bohn
>            Priority: Minor
>             Fix For: Wish List
>         Attachments: GERONIMO-2814-J2EEServerImpl.patch, JIRA-2814-2.0.patch, repo2-1.2-plan.xml,
repo2-111-plan.xml, repo2-ag20-plan.xml, repo2-ag20-plan2.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