If I run a "mvn dependency:tree" on a module with EAR packaging, I see the WARs 
that are included in the EAR, but not what's inside each WAR. With JAR 
dependencies I can always see the full dependency tree, but not with WARs. Why 
is this?

Some of these WARs do contain JARs.

If I run the dependency:tree on the module that creates the WAR then I can see 
what's inside the WAR, but not if I run it on the EAR module.

It would be useful to be able to run a dependency tree on my top module and see 
all the way to the bottom all the dependencies that are included.

Evert

Reply via email to