You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org> on 2006/05/31 18:20:30 UTC

[jira] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2 trunk)

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

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

Build instructions -  (I have used maven 2.0.4)
from top directory - 
1. mvn -N install
2. cd modules,    mvn 
3. cd m2-plugins,   mvn install
After the plugin is built, the build can be run from the top level directory using
mvn clean install  or
mvn -o clean install
configs should always be built with mvn clean install, clean is necessary for configs. this restriction will be removed soon.

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