Hi Jo, Thanks for your help. My final soultion is to create a new type of artifact - warstub - with a plugin. I put the jars, htmls, etc to these artifacts, and set the dependencies for them. When I create a war I unpack the warstub artifacts to the new war file.
Because of this bug: http://jira.codehaus.org/browse/MNG-1682 I was unable to call them warstub, I have to call them zip - otherwise the archiver does not know how to unpack it -, but everything works smoothly :) Regards, Péter -----Original Message----- From: [EMAIL PROTECTED] on behalf of Vandermeeren, Jo Sent: Fri 2007. 06. 08. 16:18 To: Maven Users List Subject: Re: War plugin transitive dependency On 6/8/07, Váry Péter <[EMAIL PROTECTED]> wrote: > > Unfortunately it does not help me in this situation: I do not have ear-s > (working with tomcat), just war-s. One portal - one war. Every module is one > war, or jar. Modules depend on each other like news.war (with jsp, html > etc) depends on HTML editor war (with other jsp, html etc), and the product > depends on news.war, with its own html-s, and jsp-s. AFAIK, dependencies of wars are not resolved transitively. If a war depends on another one, the contents of both are merged (overlayed). Nothing else to do than installing B first, to make the changes in C appear in A with the standard maven-war-plugin. However, appfuse's maven-warpath-plugin might be of interest. http://static.appfuse.org/maven-warpath-plugin/index.html It allows the dependencies of a war to be resolved transitively. Anyway, running your build from the common parent directory will guarantee a correct build reactor sequence. So there is always a last resort.. Cheers Jo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
