[
https://issues.apache.org/jira/browse/MNG-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731205#comment-17731205
]
ASF GitHub Bot commented on MNG-7572:
-------------------------------------
kwin commented on PR #833:
URL: https://github.com/apache/maven/pull/833#issuecomment-1585664405
@gnodet Any idea how to make it work with reactor builds which are both
building and using the plugin? That used to work for certain edge cases with
the old approach. Should we just fall back to pom.xml and log in the case where
the artifact is not yet built at the time where the extensions are being loaded?
> Plugin descriptor should indicate if plugin should be loaded as Maven build
> extension
> -------------------------------------------------------------------------------------
>
> Key: MNG-7572
> URL: https://issues.apache.org/jira/browse/MNG-7572
> Project: Maven
> Issue Type: Improvement
> Components: Plugin API
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Labels: plugin-descriptor-1.1
>
> Currently each consumer needs to decide if a Maven plugin should be loaded
> with extensions or without by setting the extensions value accordingly
> (https://maven.apache.org/pom.html#Plugins).
> Instead the plugin descriptor should have a flag which indicates whether the
> plugin has extensions to load which should be automatically evaluated.
> That flag should determine the default behaviour for loading extensions
> (which can still be overridden for edge cases in the pom referencing the
> plugin with extensions element).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
