[
https://issues.apache.org/jira/browse/MNG-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733706#comment-17733706
]
Herve Boutemy edited comment on MNG-7808 at 6/17/23 7:13 AM:
-------------------------------------------------------------
I'm totally lost why archetype would be broken, or anything
[~bmarwell] can you provide a reproducer project that triggers the warnings you
are talking about, please? And copy/paste the unneeded warnings in the issue
description?
I can't even get any message currently that I'm sure existed in the past
What I know is that given updates like MNG-7790 and MNG-7807, a project that
does not define any plugin version (like with minimal pom.xml) will get
different plugins versions when built with Maven 3.8.8 for example one month
ago and in one month with Maven 3.9.3 (that includes MNG-7790 and MNG-7807)
= what is called build instability, because it depends on the precise Maven 3
release used to run (then detailed bugs associated)
= what I expect we are talking about and that has been reworked so much in the
last 10 years that I'm lost about where we currently stand, then what may
eventually remain to be realistically improved
was (Author: hboutemy):
I'm totally lost why archetype would be broken, or anything
[~bmarwell] can you provide a reproducer project that triggers the warnings you
are talking about, please? And copy/paste the unneeded warnings in the issue
description?
I can't even get any message currently that I'm sure existed in the past
What I know is that given updates like MNG-7790 and MNG-7807, a project that
does not define any plugin version (like with minimal pom.xml) will get
different plugins versions when built with Maven 3.8.8 for example one month
ago and in one month with Maven 3.9.3 (that includes MNG-7790 and MNG-7807)
= what is called build instability, because it depends on the precise Maven 3
release used to run (then detailed bugs associated)
= what I expect we are talking about
> 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)
