[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414605 ]
David Jencks commented on GERONIMO-2071: ---------------------------------------- Stax removed from openejb in rev 2664. applied deploy-tool.patch, m2-plugins.patch, and the configs part of geronimo.patch, and removed stax dependency in rev 411465. There are some problems: - there are a lot of missing source geronimo-dependency.xml files. The ones generated by the m1 build don't work since they have the wrong groupId for geronimo artifacts. - As a result, the configs builds don't work after a couple of configs. - there are zillions of unneeded dependencies that should be taken care of by transitive dependency. I suspect this will be an ongoing battle. - The june 3 2006 patches were created without updating to get the changes committed on june 2. This is too hard to deal with: in the future make certain your local copy is up to date with svn before creating a patch. Either I downloaded the wrong openejb patch or the june 3 patch has no changes from the already applied june 2 patch. Please update your openejb copy and submit a patch with only the differences. > 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, 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. > (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
