[
http://jira.codehaus.org/browse/MNG-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112847
]
John Casey commented on MNG-3097:
---------------------------------
This has never worked, to my knowledge. Or at least, I can't see how we could
guarantee that any but a handful of things in that extension would be usable in
that build. This is because the lifecycle executor (and, in 2.1, the extension
scanner) pushes extensions into the core realm. When it does this, I don't
think it's particularly sensitive to artfiacts that come from within the
existing build process. I haven't looked back at the 2.0.x code on this yet,
but I'm pretty sure active artifacts are not in use, and that extensions are
all loaded up front when the lifecycle executor runs...which means that if the
extension project hasn't been built yet, and no previous artifact for that
extension is in the repository, it won't load.
Vincent, are you certain this works in 2.0.7?
> 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.1-alpha-1
> Reporter: Vincent Massol
> Fix For: 2.1-alpha-1
>
>
> 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
