Thanks Alejandro, what I meant is being able to plot the dependencies in a multi-module project. As far as I see- maven-graph-plugin generates a graph per module. Am I mistaken?
-----Original Message----- From: Endo Alejandro [mailto:alejandro.e...@grassvalley.com] Sent: 08 April 2015 17:33 To: Maven Users List Subject: RE: Looking for a way to visualize dependency structure of my multi-module pom project If by module granularity you mean excluding/including certain modules, check this pull request I did on the maven-graph-plugin that has never been and probably will never be merged to the main line (Ah the beauty of opensource, you scratch your own itch and contribute it to the community but nobody cares). It does what I think you are asking for: it introduces a list of included/excluded groupIds. https://github.com/fusesource/mvnplugins/pull/5 You would have to check it out and build it locally, but it worked fine last time I tried it over a year ago. It currently does not allow filtering based on artifactId, but if you look at the diff, you can see that it would be fairly easy to introduce that change. For me, filtering by groupId was enough since I wanted to visualize only our group's dependencies Hope it helps, Alejandro -----Original Message----- From: Pisarev, Vitaliy [mailto:vitaliy.pisa...@hp.com] Sent: Wednesday, April 8, 2015 04:46 AM To: users@maven.apache.org Subject: Looking for a way to visualize dependency structure of my multi-module pom project I have a pretty large project (~30 modules) and want to visualize module inter dependencies, excluding 3rd party. It seems that existing tools simply can't handle the maven reactor. The maven dependency plugin (dependency:tree goal) knows how to generate graphml, but only per module. And if I use the append flag, it simply shoves everything to a single file, so the output is a corrupted graphml. I also found this tool<https://github.com/janssk1/maven-graph-plugin/wiki/Manual> but it seems that there is no way to control module granularity. My last resort would be to parse the output of dependency:tree, but I thought I'll consult the community before this. DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
