[
http://jira.codehaus.org/browse/MNG-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261832#action_261832
]
Victor Dolirio Ferreira Barbosa commented on MNG-3952:
------------------------------------------------------
We have this problem too. Our component repository is in a constant update and
sometimes we change groupId and/or artifactId. Somtimes we just want to sign an
artifact as deprecated because these turned deprecated. Therefore developers
who are using these components sometimes get confused with artifacts that is
supposed to not be used.
This mechanism will be very usefull.
[]s
> Create Deprecation Mechanism for Maven Artifacts
> ------------------------------------------------
>
> Key: MNG-3952
> URL: http://jira.codehaus.org/browse/MNG-3952
> 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
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
