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 Tue, 06 Mar 2007 21:58:24 GMT

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

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

    Attachment: ServerRepository-ag20-export.zip
                ServerRepository-ag20-plan.xml

I attached a new plan with more standard names suitable for a plugin.  I deployed it locally,
and used the admin console to export the plugin.  I have attached that file, too.  I need
to do more investigation to put this in some plugin repo and test it by installing it from
there.

> 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, ServerRepository-ag20-export.zip,
ServerRepository-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.


Mime
View raw message