[
https://issues.apache.org/jira/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved MNG-3879.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Issues to be reviewed for 4.x)
> Dependency map and documentation
> --------------------------------
>
> Key: MNG-3879
> URL: https://issues.apache.org/jira/browse/MNG-3879
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.9
> Reporter: Benson Margulies
>
> This JIRA proposes a feature. I'm willing to try to contribute it given a
> modicum of encouragement and guidance.
> Over at CXF, we get many questions from users who are completely confounded
> by the complex dependency graph that results from our many dependencies and
> their many dependencies. I think that they would be less confused by far if
> maven gave them a tiny bit of help.
> My idea for this requires an addition to the core POM, which is why I'm
> starting with a JIRA here. I propose to add an 'explanation' element to the
> dependency element. This would contain a human-readable string explaining why
> the dependency is here, which could be carried out through the dependency
> plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
