[
https://jira.codehaus.org/browse/MNG-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350026#comment-350026
]
Archimedes Trajano commented on MNG-3952:
-----------------------------------------
Maven does have it, but whether central takes advantage of it or not I haven't
tested as of yet. To date I haven't found an example of this working.
http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_distributionManagement
relocation
groupId String The group ID the artifact has moved to.
artifactId String The new artifact ID of the artifact.
version String The new version of the artifact.
message String An additional message to show the user about the move,
such as the reason.
This allows you to redirect to a different groupId/artifactId and version.
Though they don't have a specific facility to say "don't even try to use this
anymore".
> Create Deprecation Mechanism for Maven Artifacts
> ------------------------------------------------
>
> Key: MNG-3952
> URL: https://jira.codehaus.org/browse/MNG-3952
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.9
> Environment: All
> Reporter: Immo Huneke
>
> An example of the sort of problem that developers currently encounter can be
> seen at
> http://blog.jonasbandi.net/2008/12/using-jpa-and-hibernate-with-maven.html. I
> have encountered similar problems in the past, e.g. trying to decide which
> version of a plugin is the current one or being unaware that an artifact I
> was using in a build had been superseded by another with a different groupId
> and artifactId.
> I feel that Maven lacks a deprecation mechanism that would make it obvious to
> everyone that they're using something out of date. The problem is that once
> an artifact (other than a snapshot) has been published, it is never supposed
> to change thereafter. But it shouldn't be impossible to devise a mechanism
> for adding deprecation and redirection to the associated metadata. It would
> then be possible for the dependency resolver to display a warning whenever a
> deprecated artifact was used in a build, either as a plugin or as a library.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
