>
> Description:
> When the WAR plugin was converted from using Ant's <war> task to
> using the <jar> task we lost the ability to use the
> ${maven.war.webxml} property to specify the location of the
> web.xml file. Not only does this reduce flexibility (the only
> place you can put web.xml is in
> ${maven.war.src}/WEB-INF/web.xml), but it prevents the token
> filtering tip (in xdocs/tips.xml) from working.
>
>
Flexibility is not necesserly a good thing.
In current shape of the plugin you are able to define pre- or post- goals
which will do the same exact thing as you patch does.
War plugin is not limiting your possibilities but if you want to do
something non standard you have to do this in non standard way.
For me this is very resonable.
Keeping web xml in location different then {maven.war.src}/WEB-INF/web.xml)
is a no standard thing.
Mandating non standard project layouts through the set of configurable
properties is imho a very bad thing
(even though many plugins are written in this way).
I am not saying that the way how maven war plugin works currently is the
best thing possible, but
if you have better idea how to structure directories or where web.xml file
should be kept - please speak out!
(Token Filtering in web.xml file is a bit different subject! I have nothing
against it!)
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
