I think I remember Jason Dillon having a similar issue with the groovy stuff.
-----Original Message----- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 12, 2007 3:33 AM To: Maven Developers List Subject: Not replacing token in plugin's parameters Hi, In the trunk of the war plugin, the artifacts can be packaged in WEB-INF/lib with a custom name, a la assembly plugin. This leads to a config like this for instance: <outputFileNameMapping> ${artifactId}.${extension} </outputFileNameMapping> This worked for a while and "suddently" (that's the weird thing) it stopped. The reason for that is maven "now" (?) resolves the tokens before injecting the value in the plugin (so for instance foo.null where foo is the artifactId of the current project instead of ${artifactId}.${extension}). Questions: - I can reproduce with Maven 2.0.5, 2.0.6 and 2.0.7 so it's something related to the plugin generation maybe? - I am wondering if I could add a tag on field-level to disable this automatic resolution Any advice, thoughts? Thanks, Stéphane [1] http://jira.codehaus.org/browse/MWAR-116 -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
