[ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon closed GERONIMO-3747. ---------------------------------- Resolution: Fixed Module parentage has been updated so that the module's parent is ../pom.xml. All bits under {{framework/\*}} are now in the {{org.apache.geronimo.framework}} groupId. Other bits under {{plugins/\*}} are still using {{org.apache.geronimo.modules}} and {{org.apache.geronimo.configs}}, which should be changed, but can wait until 2.2. In addition the {{components/\*}} and {{applications/\*}} modules have been relocated under {{plugins}}. > subprojects should use file system parent poms as parent poms in general > ------------------------------------------------------------------------ > > Key: GERONIMO-3747 > URL: https://issues.apache.org/jira/browse/GERONIMO-3747 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem > Affects Versions: 2.1 > Reporter: David Jencks > Assignee: Jason Dillon > Fix For: 2.1 > > Attachments: GERONIMO-3747-step-1.diff.zip, > GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip > > > After the move of most stuff into plugins, the parent pom is usually still > o.a.g.modules/modules or o.a.g.configs/configs. I think this is a really bad > idea. I think the main thing that needs to be changed is to move the car > plugin setup code into the root pom. However I'm not sure if this is > possible.... bit of a chicken/egg situation? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.