[
https://issues.apache.org/jira/browse/MNG-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733940#comment-17733940
]
Herve Boutemy commented on MNG-7808:
------------------------------------
now I understand that the new "plugin validation" covers many aspects I did not
know: "affects version" of this issue should be updated accordingly
is there somewhere a list of the new "plugin validations" that have been added?
(these warning have really been painful given their scope, no doc, no
preparation: so many users ask about it that I'm really tired of trying to
answer)
> Remove warnings of undefined plugin versions
> --------------------------------------------
>
> Key: MNG-7808
> URL: https://issues.apache.org/jira/browse/MNG-7808
> Project: Maven
> Issue Type: Improvement
> Components: Core, Logging
> Reporter: Benjamin Marwell
> Priority: Major
>
> h2. Actual behaviour
> Maven issues warnings about undefined plugin versions when not needed
> h2. Expected behaviour
> Maven should not issue warnings about undefined plugin versions early in a
> project build.
>
> h2. Rationale
> The release plugin will be modified to reject releases of projects which are
> not defining all plugin versions: [MRELEASE-1130] Reject release of project
> containing undefined plugin versions - ASF JIRA (apache.org)
>
> Once that is done, we can remove the warnings from core:
> 1.) There should be as few as possible warnings OOTB on new maven projects
> 2.) It is not really important for local builds to define plugin versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
