[
https://issues.apache.org/jira/browse/GERONIMO-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun resolved GERONIMO-4370.
-------------------------------
Resolution: Fixed
rev 706298: update the command tool to build the default repo to the plugin
list to be installed and update pluginInstallerGBean to take consideration of
both the default repo and source repo.
Tested using both ./gsh install-plugins and ./deploy search-plugins with
installing activemq RA onto little G (2.2-snapshot).
> improve usage of default-repository in plugin catalog
> -----------------------------------------------------
>
> Key: GERONIMO-4370
> URL: https://issues.apache.org/jira/browse/GERONIMO-4370
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.2
>
>
> We provide source-repository in plugin metadata and default-repository
> in plugin catalog.
> Currently, (I think this is how it works) when we install a plugin
> from a remote repo A, if the installation is not restricted to the
> particular repo A:
> If the plugin specifies 1+ source-repository, we'll use that and
> ignore the default-repository specified in plugin catalog.
> If the plugin doesn't specify any source-repository, we'll use the
> default-repository specified in the plugin catalog.
> I 'd like to change it to:
> If the plugin specifies 1+ source-repository, we'll use that AND the
> default-repository specified in plugin catalog.
> Discussion thread -
> http://www.nabble.com/source-repository-%28in-plugin-metadata%29-and-default-repository-%28in-plugin-catalog%29-to20022290s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
