[ http://issues.apache.org/jira/browse/GERONIMO-1677?page=comments#action_12368602 ]
Prasad Kashyap commented on GERONIMO-1677: ------------------------------------------ The geronimo-dependency-plugin is used by the following 6 maven.xml files in modules/axis modules/directory modules/installer-processing modules/installer-support modules/jetty modules/tomcat Some dependencies in the the project.xml of the above modules are tagged with a <geronimo.dependency> property that is set to true. Based on this property, the plugin generates a geronimo-service.xml in the target/etc/META-INF directory of these modules for inclusion with the module's jar. The deps listed in the geronimo-service.xml files are used by the configuration and the configuration classloader pulls into the same classloader. Issues: ----------- 1. Dain has some plans for classloader changes at which point we don't know what will happen. 2. The <dependency><property> element that was available under project.xml is no longer available under the pom.xml. So we can't mark those deps the same way. 3. m2 has transitive deps. Maybe once the deps get pruned, there is no need for a separate geronimo-service.xml. Maybe the pom.xml itself will then be good enough. Proposed Solution (to be implemented in this JIRA) ----------------------------------------------------------------------- 1. We should check in the already generated geronimo-service.xml files into the src tree of the above modules. These files should be packaged with the modules' jars. 2. We should add a comment for those special dependencies in the above 6 modules in the migrated pom.xml in case an equivalent generation has to be done in m2. 3. delete geronimo-dependency-plugin ? > geronimo-dependency-plugin deletion > ----------------------------------- > > Key: GERONIMO-1677 > URL: http://issues.apache.org/jira/browse/GERONIMO-1677 > Project: Geronimo > Type: Sub-task > 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
