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
