[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415194 ]
David Jencks commented on GERONIMO-2071: ---------------------------------------- We have a conflict with the m1 build and geronimo-dependency.xml files. Since the geronimo groupId is different in m2 than m1, we need different contents. There is currently no way to generate the content in m2, and this is likely to stay the same for the forseeable future. If you add the m2 version to the appropriate m2 location src/resources/META-INF/geronimo-dependency.xml, the m1 build uses it instead of the generated m1 version. I guess we need to change the m1 build to exclude this specific file? I added the fixed g-d.xml files in rev r412485, discovered this problem, and rolled back in rev 412487. > 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, applications.patch.zip, configs.log, > configs.log, configs.patch, configs.patch, deploy-tool.patch, > deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, > geronimo-deployment-plugin-RTC-VOTE.2.patch, > geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, > geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, > openejb.log, openejb.patch, openejb.patch, openejb.patch, 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
