You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2017/04/25 20:27:04 UTC
[jira] [Updated] (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:all-tabpanel ]
Stephen Connolly updated MNG-6206:
----------------------------------
Fix Version/s: 3.5.1-candidate
> 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)