[
https://issues.apache.org/jira/browse/MNG-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216783#comment-17216783
]
Igor Fedorenko commented on MNG-6995:
-------------------------------------
Maven would need to read the aggregator pom in order to find all modules being
aggregated and their respective configured Core Extensions. This alone would
require non-trivial changes to how Maven Core, Core Extensions and aggregator
pom interact.
"Mutually exclusive" extensions are very likely to result in subtle build
inconsistencies, e.g., stale build output files are not regenerated in _some_
cases, or build failures that happen depending on build order and timing. I
don't see this as an acceptable failure mode for generally available Maven
feature.
> 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)
