[
https://issues.apache.org/jira/browse/MNG-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212773#comment-17212773
]
Igor Fedorenko commented on MNG-6995:
-------------------------------------
Core Extensions are discovered and loaded very early during the build, before
Maven reads any projects files, iirc. This gives Core Extensions same
capabilities (mostly) as if they were part of Maven installation, but also
means Core Extensions resolution and instantiation cannot rely on anything in
pom.xml. Core Extensions are global to the build, and aggregator project can
conceivably include modules with mutually exclusive extensions. Hope this helps.
> Support core extensions in modules of aggregator projects
> ---------------------------------------------------------
>
> Key: MNG-6995
> URL: https://issues.apache.org/jira/browse/MNG-6995
> Project: Maven
> Issue Type: New Feature
> Components: Class Loading
> Affects Versions: 3.6.3
> Reporter: mike duigou
> Priority: Major
>
> 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 currently 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 should build with whatever core extensions they have defined.
> Building a module as part of an aggregator should behave not differently than
> building the module standalone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
