maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Cole (JIRA)" <>
Subject [jira] Commented: (MNG-3952) Create Deprecation Mechanism for Maven Artifacts
Date Wed, 01 Jun 2011 21:27:22 GMT


Adrian Cole commented on MNG-3952:

in jclouds, we are using artifact ids for libraries bound to cloud provider offerings.  they
sometimes rename these, so being able to gracefully deprecate a name would be helpful.

ex. org.jclouds.provider/bluelock-vcdirector -> bluelock-vcd-lab

> Create Deprecation Mechanism for Maven Artifacts
> ------------------------------------------------
>                 Key: MNG-3952
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Artifacts and Repositories, General
>    Affects Versions: 2.0.9
>         Environment: All
>            Reporter: Immo Huneke
>             Fix For: Issues to be reviewed for 3.x
> An example of the sort of problem that developers currently encounter can be seen at 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 is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message