[
https://issues.apache.org/jira/browse/MNG-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733913#comment-17733913
]
Romain Manni-Bucau commented on MNG-7808:
-----------------------------------------
[~hboutemy] gave multiple examples in the related threads but if you want a
few:
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.camel.archetypes \
-DarchetypeArtifactId=camel-archetype-java \
-DarchetypeVersion=3.20.0 {code}
You will say me that camel must pin versions and as maven core committer, you
will also recommend to not pin default plugins to ensure it works with the most
maven versions since some archetypes are not about a specific plugin but just
building a jar or war (= 100% use maven plugins so best advice is to not bound
the pom to a version).
As explained, it is more than fine to fail if we dont support a config and we
broke a plugin for whatever reason, it is not acceptable to warn for something
we are ourself responsible (we own plugin and bind them to releases so it is
intended to not be pinned).
Last: if you want reproducibility you are bound to a mvn and java version at
build time (--release does not make it better, just more tolerance) so in such
a case, versions are locked by design so forcing the locking is overall
negative for maven and does not enhance the reproducibility - only goal AFAIK -
so we don't have to keep it.
Side note: indeed you can get the same issue with pure maven archtectype until
you bind maven version to archtetype versions which is, here again, not what we
do today nor what we want probably since it breaks consumer/producer contract.
Hope it is clearer.
> 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)
