[ http://jira.codehaus.org/browse/MNG-1760?page=all ] Brett Porter reopened MNG-1760: -------------------------------
> Custom packaging type ignored when POM contains modules entry > -------------------------------------------------------------- > > Key: MNG-1760 > URL: http://jira.codehaus.org/browse/MNG-1760 > Project: Maven 2 > Type: Bug > Reporter: Aaron Anderson > > > First I have not come across any information stating that only POM's with > package type POM may have a modules section. If this is so then the following > is not a bug. > I created an extension plugin that has a custom artifact type and lifecycle > following the directions at > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > The POM that has the custom packaging type declares the plugin as an > extension in it's build section and has a dependency on two modules in two > different subdirectories, i.e > <modules> > <module>runtime</module> > <module>boot</module> > </modules> > If I go into the modules directory and run mvn install and then go up to the > project directory and run mvn install without the above module statement the > dependencies are found and the custom lifecyle is invoked and everything is > fine. However, if I add the above module declaration back in and run mvn > install expecting that all three projects will be built only the sub modules > are built correctly by the reactor but for the top level project the custom > packaging type is ignored and the project is treated as a POM package type > and is installed in the repository as such. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
