Hi Evert, 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? Because dependency tree displays the Maven dependency resolution. A war component does not have dependencies, because it contains it already. > Some of these WARs do contain JARs. Yeah, and therefore it does not have to resolve its dependencies anymore. > 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. Right. > 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. AFAICS it is not directly supported by the Maven core and the plugin would have to do it on its own. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
