[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=comments#action_12372837 ]
Anita Kulshreshtha commented on GERONIMO-1740: ---------------------------------------------- This is a Summary of the implementation to be done based on the information provided by David Jencks at http://www.nabble.com/Re%3A-Questions-about-the-packaging-plugin-t1375478.html 1.The m1 geronimo-packaging-plugin contained 4 goals : a. car:prepare-plan - Add dependencies to plan.xml b. car:package - c. car:install d. car:distribute Most configs use car:install goal. These 3 goals will be merged to give a goal "car:install". The car:distribute goal will be converted at the time of assembly. It might be necessary to implement it as discussed in 'Specifying a new packaging' at : http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html 2. The boot configuration, geronimo-gbean-deployer uses a different form of car:package goal and should be handled separately. 3. The plan.xmls will contain all the dependencies, even though m2 pom.xmls will not have the transitive dependencies.This is needed to maintain a documentaion of the dependencies of a configuration. 4. When we move to full m2 build, replace the following line in all src/plan.xml files : <configuration configId="${pom.groupId}/${pom.artifactId}/${pom.currentVersion}/car" domain="geronimo.server" server="geronimo"> with <configuration configId="${project.groupId}/${project.artifactId}/${project.version}/car" ................................> > Plugin migration to Maven 2: geronimo-packaging-plugin > ------------------------------------------------------ > > Key: GERONIMO-1740 > URL: http://issues.apache.org/jira/browse/GERONIMO-1740 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Components: buildsystem > Versions: 1.x > Reporter: Jacek Laskowski > Assignee: Anita Kulshreshtha > > It's a task to keep track of the progress of the plugin build migration to > Maven2 -- 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
