geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anita Kulshreshtha (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2 trunk)
Date Sat, 03 Jun 2006 12:44:30 GMT
     [ ]

Anita Kulshreshtha updated GERONIMO-2071:

    Attachment: openejb.patch

This openejb patch moves exisiting modules/pom.xml to openejb/pom.xml
and adds a new modules/pom.xml 
   This is for better usability. Now all units can be built from the top directory using -

mvn -Dall=modules | m2-plugins | openejb | configs  | applications (need a better name for
   -- configurations must always be built using clean followed by an install.
  -- As before after the modules and the plugins have been built once, the build can be run
 from the top directory using 
mvn -o or mvn

> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>          Key: GERONIMO-2071
>          URL:
>      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, deploy-tool.patch, geronimo.patch,
geronimo.patch, geronimo.patch, m2-plugins.patch, mvn.log, openejb.patch, openejb.patch, openejb.patch,
pom.xml, pom.xml
> A lot of work for moving Geronimo build to M2 was done under G-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:
For more information on JIRA, see:

View raw message