You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2008/10/20 16:07:44 UTC
[jira] Created: (GERONIMO-4370) improve usage of default-repository
in plugin catalog
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.
Re: [jira] Resolved: (GERONIMO-4370) improve usage of default-repository
in plugin catalog
Posted by Donald Woods <dw...@apache.org>.
Can these changes also be applied to branches/2.1?
-Donald
Lin Sun (JIRA) wrote:
> [ 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
>
[jira] Resolved: (GERONIMO-4370) improve usage of
default-repository in plugin catalog
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4370) improve usage of
default-repository in plugin catalog
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741213#action_12741213 ]
David Jencks commented on GERONIMO-4370:
----------------------------------------
Dario--
With the 2.1 series, you need to build geronimo locally on your machine or configure a plugin repository that points to an svn location that has these arttifacts (the latter is frowned upon by apache infra). The problem is that we built some private artifacts for 2.1.x and earlier but did not publish them to an accessible maven repo, so unless you do something special (build geronimo locally) geronimo can't find these artifacts. This problem is fixed in 2.2.
If the private build pluto artifact is actually in your local maven repo then there may stil bel a problem.
> 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.1.4, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.1.4, 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.
[jira] Closed: (GERONIMO-4370) improve usage of default-repository
in plugin catalog
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun closed GERONIMO-4370.
-----------------------------
Also tested change with 2.1.4-snapshot little G tomcat, able to bring JMS RA via "./deploy.sh search-plugins http://geronimo.apache.org/plugins/geronimo-2.1.4/"
> 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.1.4, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.1.4, 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.
[jira] Updated: (GERONIMO-4370) improve usage of default-repository
in plugin catalog
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun updated GERONIMO-4370:
------------------------------
Affects Version/s: 2.1.4
Fix Version/s: 2.1.4
Also added fix to 2.1 branch - rev 706391
> 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.1.4, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.1.4, 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.
[jira] Commented: (GERONIMO-4370) improve usage of
default-repository in plugin catalog
Posted by "Dario Andrade (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741169#action_12741169 ]
Dario Andrade commented on GERONIMO-4370:
-----------------------------------------
I've got littleG 2.1.4 and I still get the same error:
[root@games-server-16 geronimo]# bin/deploy.sh search-plugins http://geronimo.apache.org/plugins/geronimo-2.1.4
Using GERONIMO_HOME: /usr/local/geronimo
Using GERONIMO_TMPDIR: /tmp
Using JRE_HOME: /usr/java/default/jre
Administration
1: Geronimo Plugins, Console :: Jetty (2.1.4)
2: Geronimo Plugins, Console :: Plugin and Deployment Portlets (Jetty) (2.1.4)
3: Geronimo Plugins, Console :: Plugin and Deployment Portlets (Tomcat) (2.1.4)
4: Geronimo Plugins, Console :: Tomcat (2.1.4)
5: Geronimo Plugins, Welcome :: Jetty (2.1.4)
6: Geronimo Plugins, Welcome :: Tomcat (2.1.4)
Clustering
7: Geronimo Plugins, Clustering :: Clustering (2.1.4)
8: Geronimo Plugins, Clustering :: Farming (2.1.4)
9: Geronimo Plugins, Clustering :: WADI (2.1.4)
Connector
10: Geronimo Plugins, Connector :: Deployer (2.1.4)
Databases
11: Geronimo Plugins, System Database :: Console (Jetty) (2.1.4)
12: Geronimo Plugins, System Database :: Console (Tomcat) (2.1.4)
Debug
13: Geronimo Plugins, Debug Views :: Jetty (2.1.4)
14: Geronimo Plugins, Debug Views :: Tomcat (2.1.4)
Deployment
15: Geronimo Framework, Configs :: CLI Upgrade (2.1.4)
16: Geronimo Framework, Configs :: JSR-88 CLI (2.1.4)
17: Geronimo Framework, Configs :: JSR-88 DeploymentFactory (2.1.4)
18: Geronimo Framework, Configs :: Offline Deployer (2.1.4)
19: Geronimo Framework, Configs :: Online Deployer (2.1.4)
20: Geronimo Framework, Configs :: Plan Upgrade (2.1.4)
21: Geronimo Plugins, Hot Deploy :: Deployer (2.1.4)
22: Geronimo Plugins, J2EE :: JSR-88 EAR Configurer (2.1.4)
23: Geronimo Plugins, J2EE :: JSR-88 JAR Configurer (2.1.4)
24: Geronimo Plugins, J2EE :: JSR-88 RAR Configurer (2.1.4)
25: Geronimo Plugins, J2EE :: JSR-88 WAR Configurer (2.1.4)
26: Geronimo Plugins, J2EE :: Unavailable Client Deployer (2.1.4)
27: Geronimo Plugins, J2EE :: Unavailable EJB Deployer (2.1.4)
28: Geronimo Plugins, J2EE :: Unavailable Web Services Deployer (2.1.4)
29: Geronimo Plugins, Remote Deploy :: Jetty (2.1.4)
30: Geronimo Plugins, Remote Deploy :: Tomcat (2.1.4)
Development tools
31: Geronimo Plugins, Plan Creator :: Jetty (2.1.4)
32: Geronimo Plugins, Plan Creator :: Tomcat (2.1.4)
EJB
33: Geronimo Plugins, Corba :: Yoko ORB (2.1.4)
34: Geronimo Plugins, MEJB :: Config (2.1.4)
EJB Container
35: Geronimo Plugins, Corba :: Deployer (2.1.4)
36: Geronimo Plugins, OpenEJB :: Deployer (2.1.4)
37: Geronimo Plugins, OpenEJB :: OpenEJB (2.1.4)
Geronimo Core
38: Geronimo Framework, Configs :: Client System (2.1.4)
39: Geronimo Framework, Configs :: GBean Deployer (2.1.4)
40: Geronimo Framework, Configs :: GBean Deployer Boostrap (2.1.4)
41: Geronimo Framework, Configs :: GShell Framework (2.1.4)
42: Geronimo Framework, Configs :: GShell Geronimo (2.1.4)
43: Geronimo Framework, Configs :: GShell Remote (2.1.4)
44: Geronimo Framework, Configs :: J2EE System (2.1.4)
45: Geronimo Framework, Configs :: Plugin Management (2.1.4)
46: Geronimo Framework, Configs :: RMI Naming (2.1.4)
47: Geronimo Framework, Configs :: Shutdown (2.1.4)
48: Geronimo Framework, Configs :: Transformer Agent (2.1.4)
49: Geronimo Framework, Configs :: XMLBeans (2.1.4)
50: Geronimo Plugins, Client :: Client (2.1.4)
51: Geronimo Plugins, Client :: Deployer (2.1.4)
52: Geronimo Plugins, Client :: Security (2.1.4)
53: Geronimo Plugins, Connector :: Client transaction (2.1.4)
54: Geronimo Plugins, Connector :: Transaction Manager (JTA11) (2.1.4)
55: Geronimo Plugins, Corba :: Client Yoko (2.1.4)
56: Geronimo Plugins, Derby (2.1.4)
57: Geronimo Plugins, Spring (2.1.4)
58: Geronimo Plugins, System Database :: System Database (2.1.4)
JMS
59: Geronimo Plugins, ActiveMQ :: Broker (2.1.4)
60: Geronimo Plugins, ActiveMQ :: Console (Jetty) (2.1.4)
61: Geronimo Plugins, ActiveMQ :: Console (Tomcat) (2.1.4)
62: Geronimo Plugins, ActiveMQ :: Resource Adapter (2.1.4)
JavaEE
63: Geronimo Framework, Configs :: JavaEE Specs (2.1.4)
64: Geronimo Plugins, J2EE :: Server (2.1.4)
65: Geronimo Plugins, JavaMail :: JavaMail (2.1.4)
JavaEE deployment
66: Geronimo Plugins, J2EE :: Deployer (2.1.4)
67: Geronimo Plugins, Jasper :: Deployer (2.1.4)
Jetty
68: Geronimo Plugins, Jetty :: Clustering Builder for WADI (2.1.4)
69: Geronimo Plugins, Jetty :: Deployer (2.1.4)
70: Geronimo Plugins, Jetty :: Jetty 6 (2.1.4)
71: Geronimo Plugins, Jetty :: Jetty 6 Clustering over WADI (2.1.4)
Monitoring
72: Geronimo Plugins, Monitoring :: Agent (2.1.4)
73: Geronimo Plugins, Monitoring :: Agent DataSource (2.1.4)
74: Geronimo Plugins, Monitoring :: Agent JMX CAR (2.1.4)
75: Geronimo Plugins, Monitoring :: Console (Jetty) (2.1.4)
76: Geronimo Plugins, Monitoring :: Console (Tomcat) (2.1.4)
77: Geronimo Plugins, Monitoring :: Console DataSource (2.1.4)
Persistence
78: Geronimo Plugins, OpenJPA :: Deployer (2.1.4)
79: Geronimo Plugins, OpenJPA :: OpenJPA (2.1.4)
Plugins
80: Geronimo Plugins, Windows Service Wrapper (2.1.4)
Portals
81: Geronimo Plugins, Pluto :: Support (2.1.4)
Security
82: Geronimo Framework, Configs :: J2EE Security (2.1.4)
83: Geronimo Framework, Configs :: JMX Security Configuration (2.1.4)
84: Geronimo Framework, Configs :: Server Security Configuration (2.1.4)
85: Geronimo Plugins, CA Helper :: Jetty (2.1.4)
86: Geronimo Plugins, CA Helper :: Tomcat (2.1.4)
Shared
87: Geronimo Plugins, Shared Library (2.1.4)
Tomcat
88: Geronimo Plugins, Tomcat :: Clustering Builder for WADI (2.1.4)
89: Geronimo Plugins, Tomcat :: Clustering over WADI (2.1.4)
90: Geronimo Plugins, Tomcat :: Deployer (2.1.4)
91: Geronimo Plugins, Tomcat :: Tomcat (2.1.4)
92: Geronimo Plugins, Tomcat :: Tomcat without HA (2.1.4)
Web Framework
93: Geronimo Plugins, Dojo :: Jetty6 (2.1.4)
94: Geronimo Plugins, Dojo :: Tomcat (2.1.4)
95: Geronimo Plugins, Dojo Legacy :: Jetty6 (2.1.4)
96: Geronimo Plugins, Dojo Legacy :: Tomcat (2.1.4)
97: Geronimo Plugins, Jasper :: Jasper (2.1.4)
98: Geronimo Plugins, MyFaces :: Deployer (2.1.4)
99: Geronimo Plugins, MyFaces :: MyFaces (2.1.4)
Web Services
100: Geronimo Plugins, AXIS :: AXIS (2.1.4)
101: Geronimo Plugins, AXIS :: Deployer (2.1.4)
102: Geronimo Plugins, AXIS2 :: AXIS2 (2.1.4)
103: Geronimo Plugins, AXIS2 :: Deployer (2.1.4)
104: Geronimo Plugins, AXIS2 :: EJB (2.1.4)
105: Geronimo Plugins, AXIS2 :: EJB Deployer (2.1.4)
106: Geronimo Plugins, CXF :: CXF (2.1.4)
107: Geronimo Plugins, CXF :: Deployer (2.1.4)
108: Geronimo Plugins, CXF :: EJB (2.1.4)
109: Geronimo Plugins, CXF :: EJB Deployer (2.1.4)
110: Geronimo Plugins, JAXWS :: Deployer (2.1.4)
111: Geronimo Plugins, JAXWS :: EJB Deployer (2.1.4)
112: Geronimo Plugins, UDDI Server :: Jetty6 (2.1.4)
113: Geronimo Plugins, UDDI Server :: Tomcat (2.1.4)
114: Geronimo Plugins, Web Services :: Common (2.1.4)
Install Services [enter a comma separated list of numbers or 'q' to quit]: 81
Checking for status every 1000ms:
Downloading org.apache.pluto/pluto-portal-driver/1.1.6-G643117/jar
Installation FAILED: Could not find org.apache.pluto/pluto-portal-driver/1.1.6-G643117/
> 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.1.4, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.1.4, 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.