[
https://issues.apache.org/jira/browse/MNG-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209730#comment-17209730
]
mike duigou commented on MNG-6995:
----------------------------------
There doesn't seem to be any justification or documentation of the current
behaviour. That the core extension mechanism didn't work for aggregator modules
was surprising and greatly reduces the value of the core extension mechanism.
If I build a module independently I get extensions; if I build the same module
as part of an aggregator then I don't. So instead of being able to use an
aggregator I end up with a bash script to build each of the modules
independently and have to manually manage dependencies (yuck!).
> Core extensions ignored in modules of aggregator
> ------------------------------------------------
>
> Key: MNG-6995
> URL: https://issues.apache.org/jira/browse/MNG-6995
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 3.6.3
> Reporter: mike duigou
> Priority: Major
> Fix For: wontfix-candidate
>
>
> If you have defined core extensions using the MNG-5771 .mvn/extensions.xml
> mechanism and then include the module in an aggregator pom the extensions
> will be ignored. Only extensions defined in same directory as the aggregator
> pom will be used and those extensions will not be invoked for the modules,
> only for the aggregator itself.
> Ideally modules would have whatever extensions they defined.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)