[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=344718#comment-344718
]
Mirko Friedenhagen commented on MNG-5604:
-----------------------------------------
[~kenney], so your approach would be:
* Given two projects A and B where B depends on A.
* Create an enforcer-rule "markAsDeprecated" which only states that the current
project (A) is deprecated and is to be replaced by A2 (I would suggest a
message here). This rule should be included in project A itself, right?
* Create another enforcer-rule "banDeprecated" to be included in project B
which checks the for the existence of the "markAsDeprecated" rule in all it's
dependencies and warns or fails with a message when it finds any such
dependencies.
This could work, however it would violate the spirit of the enforcer-plugin IMO.
> 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)
