[ 
http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414138
 ] 

Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------

We use 2 legacy repository - 
   - http://www.ibiblio.org/maven - nothing found 
   - http://people.apache.org/repository/incubator-activemq/jars/
      The second one contains 4.0-SNAPSHOT under a different gropuId 
(incubator-activemq)
   The version on M2 repo (repo1.maven.org) is - 4.0M1 dt Nov 2005
http://repo.mergere.com/maven2/activemq/activemq-core/4.0-M1/
    We could use the incubator-activemq groupId, this is where the latest jar 
is. 

> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
>          Key: GERONIMO-2071
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2071
>      Project: Geronimo
>         Type: New Feature
>     Security: public(Regular issues) 
>   Components: buildsystem
>     Versions: 1.2
>     Reporter: Prasad Kashyap
>     Assignee: Jacek Laskowski
>      Fix For: 1.2
>  Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, 
> openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. 
> (http://issues.apache.org/jira/browse/GERONIMO-851) 
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and 
> hence the migration work needs to be done here again. This JIRA will seek to 
> consolidate the work that was done under G-851 and all it's subtasks. 
> The patch(es) here will be submitted under the RTC guidelines. Future patches 
> for migration will have to be applied on top of this one. This patch will 
> contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 
> with links to dev list archives.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to