You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/09/27 18:34:00 UTC
[jira] [Commented] (MNG-7508) Validate usage of true on plugins
[ https://issues.apache.org/jira/browse/MNG-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769739#comment-17769739 ]
Tamas Cservenak commented on MNG-7508:
--------------------------------------
There are cases where loading a "plain" (without extension) plugin as extension is for technical reason required (ie. to circumvent some static class loading issue), and also other way around.
So if "validate" means "emit warning", then am OK with it, otherwise if plan is to fail the build (break maven execution), then a big no for this.
> Validate usage of <extensions>true</extensions> on plugins
> ----------------------------------------------------------
>
> Key: MNG-7508
> URL: https://issues.apache.org/jira/browse/MNG-7508
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Konrad Windszus
> Priority: Major
>
> It should be validated by Maven if a Maven plugin loaded with {{<extensions>true</extensions>}} actually comes with extensions or custom lifecycle mapping requiring it to be loaded with that option. Similarly in case this flag is {{false}} (default) Maven should emit a warning if the plugin comes with extensions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)