[ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_77465 ] Kenney Westerhof commented on MNG-1915: ---------------------------------------
Personally I'm +1 on allowing any project to have a modules section. This used to be allowed in early versions of m2. That would fix this limitation. Also, it's no longer a problem with eclipse. Right now you can't add pom.xml projects to eclipse, unless you specify a workspace somewhere which will link project files. It might not work to allow this currently, though, because of cyclic dependencies. Why was this disallowed? I can't seem to find the reason in Jira. > Top level project have to have a packaging of "pom". What about plug-ins > wanting to make a different top level packaging? > ------------------------------------------------------------------------------------------------------------------------- > > Key: MNG-1915 > URL: http://jira.codehaus.org/browse/MNG-1915 > Project: Maven 2 > Issue Type: Bug > Components: Reactor and workspace > Affects Versions: 2.0.1 > Reporter: Nils Fredrik Gjerull > Fix For: 2.1 > > > The issue number MNG-764 included a patch that made maven check if the pom > containing {{<module>}} elements had a packaging of pom. What if a plug-in > want to create a different top level packaging? -- 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
