You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "benson margulies (JIRA)" <ji...@codehaus.org> on 2008/12/01 00:47:19 UTC
[jira] Created: (MNG-3879) Dependency map and documentation
Dependency map and documentation
--------------------------------
Key: MNG-3879
URL: http://jira.codehaus.org/browse/MNG-3879
Project: Maven 2
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.
The first part of the idea 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.
The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part.
--
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
[jira] Commented: (MNG-3879) Dependency map and documentation
Posted by "Daniel Kulp (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156012#action_156012 ]
Daniel Kulp commented on MNG-3879:
----------------------------------
Changing the POM format is definitely a huge deal and is something that seems to be constantly discussed on the dev list. :-( Adding stuff to the poms currently breaks users of any previous version of Maven, which is not ideal as many corporations and such are adverse to upgrading. There is an opinion of some people that anything deployed in central needs to be completely readable and usable by all versions of maven.
I'm wondering if instead of adding another element (and thus changing the pom schema/format), the parser could just be updated to save any comments in the dependency element. All old versions would just ignore it.
For the second part, that would be an enhancement of the dependency:tree plugin:
http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html
> Dependency map and documentation
> --------------------------------
>
> Key: MNG-3879
> URL: http://jira.codehaus.org/browse/MNG-3879
> Project: Maven 2
> 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.
> The first part of the idea 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.
> The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part.
--
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
[jira] Commented: (MNG-3879) Dependency map and documentation
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158434#action_158434 ]
Brett Porter commented on MNG-3879:
-----------------------------------
I agree with Daniel. Could you file a separate issue in MDEP for the second part?
Are you able to attempt the changes to retain the comments in the dependency model? You are free to create a branch of Maven 2.1.x in the sandbox to attempt this.
> Dependency map and documentation
> --------------------------------
>
> Key: MNG-3879
> URL: http://jira.codehaus.org/browse/MNG-3879
> Project: Maven 2
> 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.
> The first part of the idea 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.
> The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part.
--
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
[jira] Updated: (MNG-3879) Dependency map and documentation
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3879:
------------------------------
Fix Version/s: (was: 2.x)
3.1
POM changes get consideration for 3.1
> Dependency map and documentation
> --------------------------------
>
> Key: MNG-3879
> URL: http://jira.codehaus.org/browse/MNG-3879
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.9
> Reporter: Benson Margulies
> Fix For: 3.1
>
>
> 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.
> The first part of the idea 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.
> The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part.
--
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
[jira] Updated: (MNG-3879) Dependency map and documentation
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3879:
------------------------------
Fix Version/s: 2.x
> Dependency map and documentation
> --------------------------------
>
> Key: MNG-3879
> URL: http://jira.codehaus.org/browse/MNG-3879
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.9
> Reporter: benson margulies
> Fix For: 2.x
>
>
> 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.
> The first part of the idea 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.
> The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part.
--
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