geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4370) improve usage of default-repository in plugin catalog
Date Mon, 10 Aug 2009 07:18:14 GMT

    [ 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.


Mime
View raw message