The warpath plugin allows you to include a WAR as a JAR and get its dependencies. The war plugin does overlaying, but it doesn't allow you to depend on a WAR as if it's a JAR. Don't know if that helps or not.
On Nov 5, 2010, at 9:51 AM, Josep García wrote: > I am trying to use the maven release plugin, which seems to be very > interesting. > > I have a multi-module project, in which I use the warpath plugin to do > overlaying. This works nicely. > > However, when doing a mvn release:prepare, I get a build error on the first > module that uses warpath: > > [INFO] [INFO] Unable to find resource > 'es.isigma.firmaqui:portasigma-web:warpath:1.4.0' in repository internal > third party (http://1 > 92.168.0.10:8084/nexus/content/repositories/thirdparty) > [INFO] Downloading: > http://repo1.maven.org/maven2/es/isigma/firmaqui/portasigma-web/1.4.0/portasigma-web-1.4.0.war > [INFO] [INFO] Unable to find resource > 'es.isigma.firmaqui:portasigma-web:warpath:1.4.0' in repository central > (http://repo1.maven.or > g/maven2) > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] BUILD ERROR > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Failed to resolve artifact. > [INFO] > [INFO] Missing: > [INFO] ---------- > [INFO] 1) es.isigma.firmaqui:portasigma-web:warpath:1.4.0 > > Apparently, the release plugin does not interpret correctly the warpath > dependency. Should I upgrade to maven-war-plugin, which I've seen it has also > overlaying features? > > Josep >