geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-2814) Add a second repository to Geronimo
Date Sat, 10 Feb 2007 01:22:05 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Kirby updated GERONIMO-2814:
--------------------------------

    Attachment: repo2-ag20-plan2.xml
                JIRA-2814-2.0.patch

This patch adds a resolveToServer attribute to Maven2Repository, so that the path to the added
repository may be interpreted relative to serverBase, to make things work much better in a
multi-server instance environment.  An example plan, repo2-ag20-plan2.xml, is also attached.

I have also added a wiki page to the 2.0 doc entitled "Multiple Repositories and Server Instances"
at  http://cwiki.apache.org/confluence/display/GMOxDOC20/Multiple+Repositories+and+Server+Instances.

> Add a second repository to Geronimo
> -----------------------------------
>
>                 Key: GERONIMO-2814
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2814
>             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: 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.


Mime
View raw message