You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 15:02:03 UTC
[jira] [Commented] (MNG-6206) We should produce a WARNING by using
RELEASE, LATEST as versions
[ https://issues.apache.org/jira/browse/MNG-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069717#comment-17069717 ]
Hudson commented on MNG-6206:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> We should produce a WARNING by using RELEASE, LATEST as versions
> ----------------------------------------------------------------
>
> Key: MNG-6206
> URL: https://issues.apache.org/jira/browse/MNG-6206
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.5.0
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Priority: Minor
> Fix For: 3.5.2
>
>
> Currently we support the usage of {{LATEST}} and {{RELEASE}} as versions for dependencies. We should encourage users to use real versions or if they really like use version ranges...
> {code:java}
> public interface Artifact
> extends Comparable<Artifact>
> {
> String RELEASE_VERSION = "RELEASE";
> String LATEST_VERSION = "LATEST";
> {code}
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-PluginMetaversionResolution
--
This message was sent by Atlassian Jira
(v8.3.4#803005)