RE: Looking for a way to visualize dependency structure of my multi-module pom project

[Pisarev, Vitaliy]

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 
toolhttps://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

Looking for a way to visualize dependency structure of my multi-module pom project

[Pisarev, Vitaliy]

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 
toolhttps://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.

How to detect dependency convergence violations between *independent* projects using maven enforcer plugin

[Pisarev, Vitaliy]

When running dependency convergence with the maven enforcer 
pluginhttp://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html,
 we can easily detect that a certain project transitively depends on 2 
different versions of the same artifact.

But consider a large group that is writing plugins for the same system. And 
consider 2 teams in this group.

One team is developing plugin A and has the following dependency chain: A - B 
- C (v 1.1)

the other team develops plugin X and has the following dependency chain: X - Y 
- C (v 2.0)

Projects A and X are completely independent but in in production, both plugins 
are deployed and there is a collision. Although both teams share CI, the 
enforcer plugin does not detect this collision since collisions are detected 
only if they share a common ancestor.

(for example, if A also had: A - D - C (v 1.4), this would have been 
detected).

It seems that the solution is to define a 3rd 'super module' that will 
aggregate A and X and feed it to the enforcer plugin. I am having trouble with 
this:

I defined such a module. Added A and X as dependencies (of type 'pom') but when 
I execute the enforcer, it does not detect the collisions! It is as if the 
super pom fails to 'absorb' the transitive dependencies.

What am I missing here?

I am using maven 3.0.4.

Specifying accepted collisions for the dependencyconvergence rules

[Pisarev, Vitaliy]

Hi all,

I ran dependencyconvergence rule (of the maven-enforcer-plugin 1.3.1 pluging) 
on my huge multi module project and got a very large report specifying a lot of 
dependency collisions (there's a surprise! ;-))
On the one hand, it will take a lot of time to align all the dependencies, on 
the other hand I want the CI build to start failing only on new problems.

I did not find a way to specify exclusions for the dependencyconvergence rule. 
Is there such a feature at all?

Thanks,
Vitaliy