[
https://issues.apache.org/jira/browse/MNG-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731537#comment-17731537
]
Romain Manni-Bucau commented on MNG-7808:
-----------------------------------------
[~hboutemy] maven is about convention over configuration so `git clone && mvn
install` must work without warnings, this got broken in last releases. This
ticket is about fixing and respecting our core values.
> 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)
