[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349612#comment-349612
]
Klaus Claszen commented on MNG-5604:
Thanks for discussing my enhancement request. I never used the enforcer plugin
so far and will have a look if I could handle my use case. Nevertheless it
seems that the modul that possibly uses a deprecated module has to include
something by itself to get the deprecation hint. That could be avoided in a mor
'core' centric solution.
make it possible to mark a maven module as deprected
Key: MNG-5604
URL: https://jira.codehaus.org/browse/MNG-5604
Project: Maven
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348051#comment-348051
]
Jason van Zyl commented on MNG-5604:
I agree this can be done with the enforcer plugin.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5604.
--
Resolution: Won't Fix
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344718#comment-344718
]
Mirko Friedenhagen edited comment on MNG-5604 at 4/11/14 2:27 AM:
--
[~kenneyw], 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.
was (Author: mfriedenhagen):
[~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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344763#comment-344763
]
Kenney Westerhof commented on MNG-5604:
---
Hi Mirko,
That's pretty much it, although I would not declare A as deprecated using a
rule, since it is not applicable as a rule to project A. I'd make a split in
the configuration to distinguish rules from declarations, for example:
A's pom.xml:
{code:xml}
plugin
artifactIdmaven-enforcer-plugin/artifactId
configuration
declarations
deprecated/deprecated
/
{code}
Similar for B:
{code:xml}
plugin
artifactIdmaven-enforcer-plugin/artifactId
configuration
rules
banDeprecated/
/
{code}
I don't see how this would break the spirit of the enforcer plugin at all. In
project B it operates as usual, enforcing rules. In A it serves to provide
metadata for it's own functioning in dependent projects.
The thing with the POM is that it doesn't change much which severly impedes
adding new functionality like this issue proposes.
This solution still adheres to the idea of specifying project metadata in the
POM (both for building and using such projects), using a standard maven plugin
even, while promoting extension of the metadata provided. A feature such as
this can then be developed independently of the maven core platform and rest on
standard plugin functionality. Once it gains popularity and other plugins start
to use such metadata it can be promoted to become part of the 'static' POM
definition itself, or even be placed in a plugin configuration dedicated to
providing such extended metadata.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344780#comment-344780
]
Paul Benedict commented on MNG-5604:
Perhaps it is better to open up a new ticket at
http://jira.codehaus.org/browse/MENFORCER and keep this open in case Maven core
gets its own solution.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344710#comment-344710
]
Kenney Westerhof commented on MNG-5604:
---
Deprecation always requires a reference to the preferred solution, because if
the functionality is not provided by an alternative, the module is still useful.
The idea behind Maven is to have stable builds, producing the same result on
any system, but it does allow for automatic project metadata updates using
version ranges on dependencies.
The relocation functionality was made to cover cases such as projects not
adhering to decent versioning standards and is a different problem. In this
case it can be used to automatically update from log4j 1.2.17 to 2.0 even
though the artifactId has changed.
A project moving away from using one library in favour of another will manage
the change on it's end: by changing the dependencies and updating their code to
conform to the new API. Similarly, using version ranges resulting in an
incompatible dependency being used, either the pom or the code must be changed.
Either way, it requires manual intervention which is a pretty clear message.
That said, nothing is stopping you from adding that XML snippet to the pom, for
instance in a configuration section of a plugin. No-one said that plugin
configuration should be imperative only. My suggestion would be to add a mojo
to the enforcer-plugin which inspects the reactor models for enforcer-plugin
configuration for the deprecation information and display a notice.
This leaves whether or not to receive deprecation warnings up to the projects
using potentially deprecated dependencies, opens the door for more flexibility
without having to rely on the POM to change, and fit's with Maven's design of
providing standardized, extensible project lifecycle management.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343580#comment-343580
]
Klaus Claszen commented on MNG-5604:
Mirko Paul, thanks for the hints to the usage of the enforcer plugin. But I
think similar to the relocation element in the pom some kind of deprecated
would also be useful. The information should be provided in the artifact itself
by the author of the module and would be a first hand information. Of course
new version(s) have to be provided with this information because you can not
republish released versions.
As the author of a module I just would like to have the possibility to provide
the information that this module should not be used anymore. So far I need to
mark all classes as @Deprecated.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343612#comment-343612
]
Klaus Claszen commented on MNG-5604:
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343540#comment-343540
]
Klaus Claszen commented on MNG-5604:
Michael, I was not aware of this possibility. It is quite useful (thanks for
the hint). But the use case I have in mind is more like e.g. marking _log4j_ as
deprecated and suggest to use _log4j2_ instead. It is not about the same
artifact that moved to another location.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343543#comment-343543
]
Paul Benedict commented on MNG-5604:
I don't see how it's possible today since released POMs can't/shouldn't be
republished. However, what you want is very similar to an adjunct database that
can be amended over time. Check out this link as an example:
https://securityblog.redhat.com/2013/01/02/detecting-vulnerable-java-dependencies-at-build-time/
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343544#comment-343544
]
Mirko Friedenhagen commented on MNG-5604:
-
Klaus, we use the maven-enforcer-plugin for stuff like this, look for
bannedDependencies.
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343415#comment-343415
]
Michael Osipov commented on MNG-5604:
-
Have you seen this?
http://maven.apache.org/ref/3.2.1/maven-model/maven.html#class_relocation
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
Klaus Claszen created MNG-5604:
--
Summary: 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
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5604) make it possible to mark a maven module as deprected
[
https://jira.codehaus.org/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Claszen updated MNG-5604:
---
Labels: build pom.xml (was: )
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
reasonnot maintained anymore/reason
instead
groupIdfoo/groupId
artifactIdbar/artifactId
/instead
/deprecated
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
