About the JSP use case, although you could filter the entire set of
jsps, based on the info you gave I still think it's a bad idea. You
would need to package different war files for different deployments. I
like more the idea of a common war with external configuration based
on the stage, profile
Carlos,
It's not just JSPs first of all. ${} is a pretty common syntax used
for various templating and expression evaluation needs. For example, you
might see that in a Spring application context file when somebody uses
PropertyPlaceHolderConfigurer to externalize some values to a separate
Colin, can you explain what's the use case here?
I don't see the probelm with JSPs because you would at most filter the
web.xml setting a parameter that is later accessed at runtime from the
jsps. I can't think about a use case where you would need to filter
all the jsps at build time.
On 4/29/0
Wayne,
This is not really true any longer, as of this fix:
http://jira.codehaus.org/browse/MWAR-12
you can filter with the WAR task too.
In any case, I was making a general point about conflicting with
application template files of any sort (not just JSPs) that use the
${} syntax. It's a
On 4/29/2006 4:55 PM, Simon Kitching wrote:
On Sat, 2006-04-29 at 16:09 -0400, Colin Sampaleanu wrote:
Hi,
When turning on filtering for resources in Maven2, is there any way to
override the default filter string pattern of '${token}'? I can't find
any mention of any way to customize thi
JSP files etc are not "resources" but rather should be stored in the
/src/main/webapp folder and thus not processed as "resources".
So I'll disagree with your statement. And I have no idea how/where to
modify the "default filter string pattern" if it is even possible.
Wayne
On 4/29/06, Colin Sa
On Sat, 2006-04-29 at 16:09 -0400, Colin Sampaleanu wrote:
> Hi,
>
> When turning on filtering for resources in Maven2, is there any way to
> override the default filter string pattern of '${token}'? I can't find
> any mention of any way to customize this, in any docs.
>
> The use of ${token}
Hi,
When turning on filtering for resources in Maven2, is there any way to
override the default filter string pattern of '${token}'? I can't find
any mention of any way to customize this, in any docs.
The use of ${token} as a token is IMHO a really bad choice, given the
fact that it's such
