[
https://issues.apache.org/jira/browse/MNG-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733865#comment-17733865
]
Herve Boutemy commented on MNG-7808:
------------------------------------
[~romain.manni-bucau] I asked for concrete example of warnings: I said I was
not able to get them any more.
quickstart archetype has been updated to do the right thing, even if, yes, it
is cumbersome
bq. So overall we should probably just keep our philosophy and work OOTB
without any side effects which don't enhance the user stability but keep it at
status quo with the same downside than not having them.
this sentence is so complex, when we can't be clear on simple things, that I
don't know what to understand from it: keep the warnings (once we have
clarified them) or not?
> 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)
