I didn't see one, so I added one. Refer to http://jira.codehaus.org/browse/MWAR-194.
Thanks. Brad -----Original Message----- From: Mark Hobson [mailto:markhob...@gmail.com] Sent: Wednesday, May 13, 2009 3:37 AM To: Maven Users List Subject: Re: War Overlays and Conflicting Jars 2009/5/12 Brad Harper <brad.har...@epsiia.com>: > 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>. Fancy raising an issue against the War Plugin to warn/error for this situation, if there's not one there already? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
