You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2017/05/20 09:34:04 UTC

[jira] [Comment Edited] (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=16018383#comment-16018383 ] 

Karl Heinz Marbaise edited comment on MNG-6206 at 5/20/17 9:33 AM:
-------------------------------------------------------------------

Sure if you like go for it....But only a single issue which means here only MNG-6206


was (Author: khmarbaise):
Sure if you like go for it....

> 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
>            Priority: Minor
>             Fix For: 3.5.1-candidate, 3.6.0
>
>
> 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
(v6.3.15#6346)