[
https://issues.apache.org/jira/browse/MNG-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036359#comment-16036359
]
ASF GitHub Bot commented on MNG-6206:
-------------------------------------
Github user khmarbaise commented on the issue:
https://github.com/apache/maven/pull/121
Please make a complete commit message with reference to the appropriate
ticket.
```
[MNG-6206] display deprecation build warning in case when dependencies use
metaversions (LATEST or RELEASE)
Maybe some explantations/descriptions if needed
```
I have applied your patch on a branch MNG-6206 to check via the integration
tests. I have modified the commit message see here:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=eb6b212b567c287734a2dbbef3c113fe650f1def
Waiting on the results of the integration tests.
> 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)
