I also needed some functionality that has been added to the
maven-war-plugin but hasn't been released yet (i.e. it is not in
maven-2.0.4).
I grabbed the source tree for maven-war-plugin from subversion and added
it to my project as another module (with a README file to tell my team
not to modify it, and that it can be removed after the next maven
release). My experience was that simply adding the plugin module to my
project (including adding it as a module in the parent pom) caused the
build to use it (rather than using a released version of
maven-war-plugin) -- no further configuration was necessary.
Perhaps there is a better way to do it. Maybe using a snapshot of
maven-war-plugin or something. But I am not sure how to do that, or even
if there is a snapshot of maven-war-plugin available.
-Max
Jorg Heymans wrote:
Hi,
According to [1], it should now be possible to apply standard resource
filtering to war resources. I haven't been able to get this to work
however,
and the issue is not clear on exactly how one can take advantage of the
fix.
There is ofcourse the workaround using a temporary directory to write the
filter results to, as suggested here [2], but i'ld rather just use the
standard mechanism now that it has been fixed.
Any ideas on how to get this to work ?
Regards
Jorg
[1] http://jira.codehaus.org/browse/MWAR-12
[2] http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28129
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
