[ http://jira.codehaus.org/browse/MNG-459?page=all ]
Brett Porter closed MNG-459:
----------------------------
Resolution: Won't Fix
m2 uses the parent tag - it is used to assemble inheritence by incorporating
tags from the parent. It builds fine standalone, because the parent is
published to the repository.
The child references you are looking for are <modules/>, which trigger
subbuilds from the parent.
> <parent> tag ignored for single module
> --------------------------------------
>
> Key: MNG-459
> URL: http://jira.codehaus.org/browse/MNG-459
> Project: Maven 2
> Type: Improvement
> Reporter: Edwin Punzalan
> Priority: Trivial
>
>
> Currently, to do multiple modules, you need to go through all the pom.xml of
> each module and add the <parent> tag. Actually this is fine, but then
> pom.xml should be distributable, right?
> What I mean is, if I want to distribute a single module named Xmodule from an
> m2 group project, then the pom.xml of Xmodule would contain the <parent> tag
> which is not relevant and I found m2 to be ignoring it anyway.
> So, instead of putting a <parent> tag, maybe its better to reverse the
> configuration by just adding a <child> tag on the parent pom.xml. This way,
> the child modules can be distributed without the <parent> tags.
--
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]
