[
http://jira.codehaus.org/browse/MNG-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3097:
Affects Version/s: 2.0.x
2.0.4
2.0.5
2.0.6
2.0.7
Fix Version/s: (was: 2.1-alpha-1)
2.x
I'm not sure we'll ever have an elegant way to solve this problem. Part of the
snag is that extensions by definition change the way the build runs. If the
extension is meant to be part of the build, then we have the potential for a
chicken-and-egg scenario where the extension is built and then modifies the
build to exclude its own module (in the case of a profile activator, for
example).
In any case, this is not a regression, so I'm moving it a little further out so
we can do some discussion and design work.
> Build extension not working if not placed in the pom.xml where a reactor
> build is initiated
> ---
>
> Key: MNG-3097
> URL: http://jira.codehaus.org/browse/MNG-3097
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.x, 2.1-alpha-1
>Reporter: Vincent Massol
> Fix For: 2.x
>
>
> If I have a multi module build and if the build extension is located in one
> of the sub modules being built it's ignored. It has to be placed in the
> pom.xml where the multi module build is initiated to be taken into account.
--
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
