Pepper reports with perpetrating plugins
----------------------------------------
Key: MDEP-302
URL: http://jira.codehaus.org/browse/MDEP-302
Project: Maven 2.x Dependency Plugin
Issue Type: New Feature
Components: tree
Affects Versions: 2.2
Reporter: Benson Margulies
Assignee: Brian Fox
Barrie Treloar recommended that I translate some recent confusion into a JIRA.
Here goes.
Step 1: run mvn on a project. Get told that the desired version of a dependency
was not available. The problem was that a group ID from jetty6 had somehow
ended up combined with a version suitable for jetty7.
Step 2: waltz around all the seemingly relevant POMs once, find nothing.
Step 3: run m3 with -X. Aha: a clue. A line stating that the this dependency
had been 'managed' from one version to another. Of course, due to -X, this was
buried in an avalanche of hard-to-read logging.
Step 4: rummage some more, and find some stale dependency management in a
parent POM that applied a property that I now use for jetty7 with the jetty6
groupId.
This problem would have been found in an instant if mvn dependency:tree were
annotated with 'management' information: is the version chosen via
dependencyManagement, and, if so, FROM WHICH POM.
--
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
