[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414538 ]
David Jencks commented on GERONIMO-2071: ---------------------------------------- I've applied parts of some of these patches: openejb.patch dated 02/june/06 applied in openejb rev 2663 geronimo.patch dated 01/june/06 applied the parts for modules and m2-plugins. Have not committed the configs parts, waiting for a PluginBootstrap2 class that does not conflict with the one for m1. geronimo rev 411333. For me all the tomcat tests fail, I had to run with mvn -Dmaven.test.skip=true. It did not look to me like the openejb tests were running at all, even with plain mvn install. Also I updated 2 versions in /pom.xml, commons-modeler and axis, to the versions currently in the m1 build. I think that the applications reorganization should proceed by a committer executing the svn mv operations so we preserve svn history. I doubt that patch can do this. Exactly how to proceed with this part needs a little more discussion. > 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: applications.patch.zip, deploy-tool.patch, geronimo.patch, > geronimo.patch, geronimo.patch, openejb.patch, openejb.patch, pom.xml, 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
