Hi all,
I am having problems filtering my resources (.jsp, .xml, .sql). I configure
the context path as well as URLs and so I would like to keep these as
variables so I can update the property in a single place and everything will
be updated automatically.
The issue that I am having is that wherever I use certain attributes:
[code]
${users.id}
${user.id}
${adfadfadflkadf.id}
[/code]
They all match the same pattern unfortunately resulting in an incorrect
override. I do not want these variables in my JSPs to be matched, but I
want ${context.path} to be matched and it is being matched correctly. Is
there any way to restrict pattern matching to strict, or is this a bug with
the plexus matching code base?
Please let me know if there is another viable option to filter these
resources. The maven-war-plugin basically extends the maven-filtering
plugin and are both based off of the plexus pattern matching plugin and that
appears to be causing the problems.
Is it possible to change the pattern matching format as well to only allow
@variable.property@ and not ${variable.property}? This way, my JSPs can
still use ${} without being adversely affected.
Thanks,
Walter
--
View this message in context:
http://www.nabble.com/maven-war-plugin-%28filtering-resources%29-tp19434177p19434177.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
