I am currently using the latest WAR plugin (1.6) and I found some strange behaviour. On the first build of a WAR for a webapp everything works fine, but on every consecutive run the plugin updates the WAR file (I guess for performance reasons) and starts to produce duplicate Class-Path Attribute entries in the MANIFEST.MF file, and on every update they get more and more. On deployment, JBoss complains about this and won't deploy the webapp anymore.
Is that a bug? The update seems to work for every other attribute in the manifest, so why not for Class-Path?
Could we not just include a further property, like ${maven.war.update} to have control over the WAR creation process?
Thanks, Leander
--
GnuPG Fingerprint = FC88 7806 111C 9DD5 1136 B311 EF00 4F8F A6D1 DC79
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
