Are you running dependency:tree from a top-level build that includes both other builds via a parent POM? That's what I do, reactor does the right thing and dumps all the builds it finds.
Personally, I believe this is the correct behavior, I wouldn't want a reactor dump of such a build to analyze the WAR build twice. $0.02... On May 17, 2011, at 7:52 AM, Evert Hoff wrote: > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
