[ http://issues.apache.org/jira/browse/GERONIMO-1677?page=comments#action_12369756 ]
David Jencks commented on GERONIMO-1677: ---------------------------------------- I believe the only plausible short term strategy for m2 is to check the geronimo-service.xml files generated by the m1 dependency plugin into src. We can revisit this when we have a DirectedAcyclicGraphClassloader as planned for the future. The problem is that with our current classloader structure, a jar including a geronimo-service.xml file is included in a configuration, which also has a bunch of parents (imports). Often many of the m2-required compilation dependencies are also included in one of the parent classloaders. Thus the geronimo-service.xml contains the m2 dependencies with the jars supplied by parents removed. For m2, we could probably include the parent configurations as dependencies to get the same effect, and then geronimo-service.xml would actually have the jar dependencies from pom.xml, but this would involve mixing together the modules and configs builds. My conclusion is that the current generated files need to be checked in, and after the build is working smoothly we can revisit the problem. > Plugin migration to Maven 2: geronimo-dependency-plugin > ------------------------------------------------------- > > Key: GERONIMO-1677 > URL: http://issues.apache.org/jira/browse/GERONIMO-1677 > Project: Geronimo > Type: Sub-task > Components: buildsystem > Versions: 1.x > Reporter: Prasad Kashyap > -- 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
