Jeff MAURY wrote: > On Jan 15, 2008 3:15 PM, Nigel Magnay <[EMAIL PROTECTED]> wrote: > >> The Mojo Developer Cookbook >> (http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook) >> is great. >> >> In it, there's a section on "Resolving Transitively". This works >> great - however, the artifact set that is resolved is based on >> Maven's idea of which graph edges ought to be considered for >> resolution. >> >> For example, if I have a WAR file, then any declared dependencies >> that are JARs (and POM I think) are included, and those artifacts >> have their dependencies added to the list (and so on, recursively). >> The end result resolves to a single version for each JAR artifact. >> >> However - if the WAR file has a WAR dependency, then it will not be >> considered, and any JAR files in there won't be included in the set >> that the version is resolved in. > > This is not what I have from my experience. If a WAR POM has > a dependency of > type war, then then content of this dependency will be copied > verbatim to the target folder.
This was not about a *copy* it was about *resolution*. If the dependend war contains foo-1.2 and the local one depends on foo-1.3 you end up with both. >> This is the behaviour that I want, where I have a WAR of WARs, and I >> want to calculate the resolved set of dependencies. We always exclude WEB-INF/lib/*.* from the dependend wars and redeclare the deps. >> a) How can I interject my own requirements for dependency traversal? >> b) Is / how is this changed in 2.1 - all the methods on >> ArtifactResolver have been condensed down into 1.. See also MWAR-33 for discussion and workarounds. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
