You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Samuel Le Berrigaud (JIRA)" <ji...@codehaus.org> on 2008/02/17 01:57:28 UTC
[jira] Created: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Outputting dependency resolution/tree in a well known _machine readable_ output format
--------------------------------------------------------------------------------------
Key: MDEP-145
URL: http://jira.codehaus.org/browse/MDEP-145
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: resolve, tree
Affects Versions: 2.0
Reporter: Samuel Le Berrigaud
Assignee: Brian Fox
Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
The format could be xml, json or something else. I've been playing with the current output to make it so that:
* the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
* every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
This already is easy to parse.
What do you think?
--
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] Issue Comment Edited: (MDEP-145) Outputting dependency
resolution/tree in a well known _machine readable_ output format
Posted by "jerome creignou (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155118#action_155118 ]
jerome creignou edited comment on MDEP-145 at 11/23/08 9:27 AM:
----------------------------------------------------------------
Here is a patch for maven-dependency-plugin and maven-dependency-tree projects to enable output of various graph format. This patch also add support for TGF and GRAPHML formats.
maven-dependency-plugin:
* Added a 'outputType' parameter to TreeMojo to enable output format selection. Possible values are 'tgf' and 'graphml'. Default format is current console output.
maven-dependency-tree:
* Added two visitors to support TGF format and GRAPHML format.
* Refactored SerializingDependencyNodeVisitor to reuse writer initialisation.
usage :
$> mvn org.apache.maven.plugins:maven-dependency-plugin:2.1-SNAPSHOT:tree -DoutputType=graphml -DoutputFile=target/dependencies.graphml
Sample result :
http://jcreigno.free.fr/images/maven-dependency-plugin.png
(I use YED to render graph.)
was (Author: jcreigno):
Here is a patch for maven-dependency-plugin and maven-dependency-tree projects to enable output of various graph format. This patch also add support for TGF and GRAPHML formats.
maven-dependency-plugin:
* Added a 'outputType' parameter to TreeMojo to enable output format selection. Default format is current console output.
maven-dependency-tree:
* Added two visitors to support TGF format and GRAPHML format.
* Refatored SerializingDependencyNodeVisitor to reuse writer initialisation.
usage :
$> mvn org.apache.maven.plugins:maven-dependency-plugin:2.1-SNAPSHOT:tree -DoutputType=graphml -DoutputFile=target/dependencies.graphml
Sample result :
http://jcreigno.free.fr/images/maven-dependency-plugin.png
(I use YED to render graph.)
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Attachments: MDEP-145.zip
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "Alexander Syedin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Syedin updated MDEP-145:
----------------------------------
Attachment: MDEP-145-velocity.patch
I've added basic support for velocity templates to dependency:resolve / dependency:list mojos - see MDEP-145-velocity.patch attached.
This approach provides greater level of flexibility, allowing user to define arbitrary output format by himself in runtime.
for example, to get output in pom-like format one needs to create following template:
------------------
<dependencies>
#foreach( $artifact in $resolvedDependencies )
<dependency>
<artifactId>$artifact.getGroupId()</artifactId>
<groupId>$artifact.getArtifactId()</groupId>
<version>$artifact.getVersion()</version>
</dependency>
#end
</dependencies>
------------------
and then run resolve mojo:
------------------
mvn maven:resolve -DinputTemplate=path/to/template -DoutputFile=path/to/output
------------------
where path/to/template is either relative path on filesystem or path to resource in classpath. Unfortunately, Unfortunately, Velocity doesn't play well with absolute paths :(
The same approach could be expanded to:
- dependency:analyze*
- dependency:sources
- dependency:tree
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145-velocity.patch, MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree
in a well known _machine readable_ output format
Posted by "luke w patterson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184141#action_184141 ]
luke w patterson commented on MDEP-145:
---------------------------------------
Any plans to output XML POMish format?
<dependencies>
<dependency>
<groupId>fooGroupId</groupId>
<artifactId>fooArtifactId</artifactId>
<version>1</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>barGroupId</groupId>
<artifactId>barArtifactId</artifactId>
<version>1</version>
<scope>test</scope>
</dependency>
</dependencies>
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree
in a well known _machine readable_ output format
Posted by "Pi Song (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165643#action_165643 ]
Pi Song commented on MDEP-145:
------------------------------
This is such a useful new feature. Where are committers!!!
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Attachments: MDEP-145.zip
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "jerome creignou (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jerome creignou updated MDEP-145:
---------------------------------
Attachment: MDEP-145.zip
Here is a patch for maven-dependency-plugin and maven-dependency-tree projects to enable output of various graph format. This patch also add support for TGF and GRAPHML formats.
maven-dependency-plugin:
* Added a 'outputType' parameter to TreeMojo to enable output format selection. Default format is current console output.
maven-dependency-tree:
* Added two visitors to support TGF format and GRAPHML format.
* Refatored SerializingDependencyNodeVisitor to reuse writer initialisation.
usage :
$> mvn org.apache.maven.plugins:maven-dependency-plugin:2.1-SNAPSHOT:tree -DoutputType=graphml -DoutputFile=target/dependencies.graphml
Sample result :
http://jcreigno.free.fr/images/maven-dependency-plugin.png
(I use YED to render graph.)
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Attachments: MDEP-145.zip
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree
in a well known _machine readable_ output format
Posted by "luke w patterson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229685#action_229685 ]
luke w patterson commented on MDEP-145:
---------------------------------------
pretty cool, Alexander
flexible approach
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145-velocity.patch, MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "Pi Song (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pi Song updated MDEP-145:
-------------------------
Attachment: treegraph.patch
I added support for my favourite DOT format + unit tests.
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MDEP-145:
---------------------------
Fix Version/s: 2.2
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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] Closed: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly closed MDEP-145.
---------------------------------
Resolution: Fixed
r1143067 includes the missing documentation update
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: https://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.3
>
> Attachments: MDEP-145-velocity.patch, MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-145) Outputting dependency resolution/tree
in a well known _machine readable_ output format
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165791#action_165791 ]
Brian Fox commented on MDEP-145:
--------------------------------
branch merged and snapshot deployed (to new snapshot repo: http://repository.apache.org/snapshots/)
The ticket needs to stay open until the site docs are updated.
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree
in a well known _machine readable_ output format
Posted by "Pi Song (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165754#action_165754 ]
Pi Song commented on MDEP-145:
------------------------------
I branched from the latest trunk and applied the patch.
http://svn.apache.org/repos/asf/maven/sandbox/branches/MDEP-145/
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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: (MDEP-145) Outputting dependency resolution/tree in
a well known _machine readable_ output format
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MDEP-145:
---------------------------
Fix Version/s: (was: 2.2)
2.3
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.3
>
> Attachments: MDEP-145-velocity.patch, MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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] Issue Comment Edited: (MDEP-145) Outputting dependency
resolution/tree in a well known _machine readable_ output format
Posted by "Pi Song (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165664#action_165664 ]
Pi Song edited comment on MDEP-145 at 2/15/09 2:43 AM:
-------------------------------------------------------
I added support for my favourite DOT format + unit tests.
Note: This patch includes changes in the previously posted patch.
was (Author: pi_song):
I added support for my favourite DOT format + unit tests.
> Outputting dependency resolution/tree in a well known _machine readable_ output format
> --------------------------------------------------------------------------------------
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
> Affects Versions: 2.0
> Reporter: Samuel Le Berrigaud
> Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file. However the file output doesn't follow any specific format, except from being the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could leverage the dependency resolution/tree. I am thinking for example of continuous integration tools that could report on added/removed/updated dependencies on modules.
> The format could be xml, json or something else. I've been playing with the current output to make it so that:
> * the first line describes the current module for which dependency resolution is done, formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>}}
> * every following line is a dependency (indented by 2 or more spaces), formatted as such: {{<groupId>:<artifactId>:<packaging>:<version>:<scope>}}
> This already is easy to parse.
> What do you think?
--
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