[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343612#comment-343612
]
Klaus Claszen edited comment on MNG-5604 at 3/25/14 8:49 AM:
-------------------------------------------------------------
Mirko, as the author of a module I would like the possibility to mark a module
(beginning at some point of the version history and not touching existing
artifacts) as deprecated. This is very similar to marking a class or method
deprecated.
Of course the user needs to update to a recent version of the module to get the
deprecation hint - but I hope that the version check of dependencies will be
done anyway from time to time.
In fact the only relevant use case that I have in mind is to make clear that a
module will not be maintained anymore. log4j(1) might be a good use case
example. In this case I would deploy a "last" version 1.2.18 that just adds the
deprecation flag (relocation won't fit here because log4j2 is not backwards
compatible as far as I understand).
The circumstances where an author decides to mark a module as deprecated are
probably rare although I suppose there are a lot of modules that would deserve
it.
was (Author: k.claszen):
Mirko, as the author of a module I would like the possibility to mark a module
(beginning at some point of the version history and not touching existing
artifacts) as deprecated. This is very similar to marking a class or method
deprecated.
Of course the user needs to update to a recent version of the module to get the
deprecation hint - but I hope that the version check of dependencies will be
done anyway from time to time.
In fact the only relevant use case that I have in mind is to make clear that a
module will not be maintained anymore. log4j(1) might be a good use case
example. I this case I would deploy a "last" version 1.2.18 that just adds the
deprecation flag (relocation won't fit here because log4j2 is not backwards
compatible as far as I understand).
The circumstances where an author decides to mark a module as deprecated are
probably rare although I suppose there are a lot of modules that would deserve
it.
> 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)
