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] Closed: (GERONIMO-4656) Get all our private artifacts into public repos
Date Fri, 24 Jul 2009 07:14:14 GMT

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

David Jencks closed GERONIMO-4656.
----------------------------------

    Resolution: Fixed
      Assignee: David Jencks

rev 797348 removed svn repo, use of contents has been gradually eliminated.

> Get all our private artifacts into public repos
> -----------------------------------------------
>
>                 Key: GERONIMO-4656
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4656
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>            Priority: Blocker
>             Fix For: 2.2
>
>
> One idea behind maven central repo is that the dependencies have transitive closure.
 This means no private artifacts.  Maven is talking about enforcing this policy.  Currently
it causes near-infinite headaches for people trying to assemble severs without building g.
themselves from source.
> IIUC the maven policy is -- we release it -- we use our groupId.  Simple.
> Alternatively we can try to get the projects in question to release stuff themselves.
> dunno if we want to try git for applying patches to source dynamically rather than copying
over the entire svn tree.

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