[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343595#comment-343595
]
Mirko Friedenhagen commented on MNG-5604:
-----------------------------------------
Klaus, I think I do not understand the usecase correctly :-)
* Existing artifacts are "untouchable" (with some exceptions, which were
clearly wrong, see https://issues.sonatype.org/browse/MVNCENTRAL-244 for an
example :-)).
* Do you want to break the build or just warn?
So:
* Say you have a module foo-1.0.
* Now when you create foo-1.1 (or even foo-1.0.1), I would consider foo-1.0 to
be deprecated.
* So you would create a micro-version 1.0.1 which just states, that foo-1.0 is
deprecated?
* When the new library is backwards compatible, you might get away with above
relocation.
* The user has to update her pom anyway to get this message :-).
> make it possible to mark a maven module as deprected
> ----------------------------------------------------
>
> Key: MNG-5604
> URL: https://jira.codehaus.org/browse/MNG-5604
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Artifacts and Repositories
> Affects Versions: 3.2.1
> Reporter: Klaus Claszen
> Priority: Minor
> Labels: build, pom.xml
>
> It would be great if it would be possible to mark a maven module as
> 'deprecated'. It would help to document that a module is outdated. The
> information could be used during build processes to show warnings and guide
> the user to a better alternative.
> Maybe it could be a pom enhancement linke this
> {code:xml}
> <deprecated>
> <reason>not maintained anymore</reason>
> <instead>
> <groupId>foo</groupId>
> <artifactId>bar</artifactId>
> </instead>
> </deprecated>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
