Repository deprecation: When a mvn build uses a maven repository that is marked
deprecated in the maven repository metadata, it should show a warning.
------------------------------------------------------------------------------------------------------------------------------------------------------
Key: MNG-5115
URL: http://jira.codehaus.org/browse/MNG-5115
Project: Maven 2 & 3
Issue Type: New Feature
Components: Artifacts and Repositories
Affects Versions: 3.0.3
Reporter: Geoffrey De Smet
The old garbage JBoss repository is still used in many recent pom's (directly
or indirectly through dependencies).
To be able to battle it's use, a repository should be able to be marked as
deprecated.
Then when running a mvn build that somehow uses such a deprecated repository,
we should see something like this:
{code}
$ mvn clean install
[WARNING] You are using a deprecated repository
(http://deprecatedrepo.org/maven2/)
which was added in the pom of dependency org.foo:bar:1.0 ->
jdom:jdom:0.1 -> log4j:log4j:0.7
{code}
Note that it clearly shows the dependency graph path to the dependency pom that
included that bad repository.
--
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
