I recently added the buildnumber-maven-plugin (1.0-beta-1) to my build, in order to add the subversion revision number to the war file generated by maven-war-plugin (2.0.2).

The buildNumber is created correctly, and resolves fine in both the <finalName> section of the build tag, and also in the maven-war- plugin. The resulting file has the correct filename and the manifest the right entries.

What doesn't work is integrating the buildNumber property with the cargo-maven2-plugin. It is simply not resolved, resulting in the cargo-maven2-plugin (0.3.1) failing and reporting; org.codehaus.cargo.container.ContainerException: Failed to deploy [/ Users/tommy/..../web/target/web-1.0-SNAPSHOT.${buildNumber}.war] to [/ opt/resin/webapps]

Is this a known issue in the cargo-maven2-plugin? Does anyone have a workaround? I searched the archives and didn't find a mention of it.

Thanks,

\tommy


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to