Yes that works. The only mod I had to make was adding a filter file.
http://jira.codehaus.org/browse/MWAR-12
shows the filters in the configuration element of the maven-war-
plugin, which _doesn't_ work. Moving the filters element up to be a
child of the build element is the necessary fix.
There would still appear to be a problem though - how can you get
access to, say, ${project.version}. It would seem you would need to
take a resource, filter it normally, then use the filtered resource
as the filter file for the war plugin. Or how can you access a
property set in a profile? These should all be available for
filtering, and we shouldn't need to specify a filter file, if we want
to be consistent with regular resource filtering.
Should I file a JIRA issue, or are there more hidden gems that I'm
missing?
Thanks,
J
On 16-May-06, at 2:14 AM, Jorg Heymans wrote:
You need to make sure you add a filter. Below config works file for
me.
<build>
<filters>
<filter>your filter file here</filter>
</filters>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
...
</plugin>
</plugins>
</build>
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
