I was hoping to hear someone say that the war file should generate an error or fail.
In our case, we have multiple versions of a general 'platform', each represented by a war artifact. Derivative wars artifacts are built with customizations and tailorings using a war overlay. When it becomes necessary to fix or otherwise re-work a platform and re-release a corresponding derivative, we need to exactly re-construct dependencies of the original platform artifact [or risk including multiple versions] when building a new one-off. Unfortunately, the platform projects themselves are intermediate children of a multi-module project and inherit from a <dependencyManagement> element defined by that top-level [so that the latest version of a platform uses the currently preferred versions of various dependencies.] We must crack the war and meticulously re-create the dependencies of the original platform when re-building. It would nice, at least, if a build could systemically determine that a potential error has been introduced. On the other hand, maybe we should re-think our use of <dependencyManagement>. Thanks. Brad Mark Hobson wrote: > > dependency:tree doesn't currently show overlaid war jars. The war > overlay concept is conceptually outside of the normal dependency > mechanism, hence the possibility of ending up with two versions of the > same dependency. > > Anyone aware of an issue about this? The war plugin should really > fail the build, or at least warn, if the package war contains multiple > versions of the same jar. > > Mark > > 2009/5/12 Nayan Hajratwala <na...@chikli.com>: >> mvn dependency:tree should let you see that there are 2 of the same jars, >> but it won't "alert" you. >> >> A better solution might be to use a <dependencyManagement> section in the >> parent pom of both modules in which you specify the jar versions. That >> way >> you won't have the problem of using different versions in different >> modules. >> >> --- >> Nayan Hajratwala >> http://agileshrugged.com >> http://twitter.com/nhajratw >> 734.658.6032 >> >> On May 11, 2009, at 3:55 PM, Harper, Brad wrote: >> >>> Is there a way to detect when the dependencies of two war artifacts are >>> inconsistent with respect to packaged jar versions? >>> >>> >>> >>> E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed >>> where an inconsistent dependency on abc-1.0.1.jar is also defined. >>> >>> >>> >>> The resulting war will contain both jar files and, so far as I can tell, >>> the subsequent behavior is indeterminate. >>> >>> >>> >>> Brad >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://n2.nabble.com/War-Overlays-and-Conflicting-Jars-tp2867314p2871095.html Sent from the maven users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
