I confirmed that resource filtering is only happening to the files are
targeting. I also made just to run the maven install with -X to make sure
that the filtering was only happening the specified resources.
If I explode the war file it contains the jsp files that still contain the
${name} and ${url} references. By removing the pom.xml and pom.properties
from the war everything works as expected. Someone brought up a point about
JDK 1.6 and xml based properties files and how it might be something
reading the pom.xml. We haven't been able to figure out what would be
causing it.
-Matt
On Wed, May 23, 2012 at 7:23 PM, Barrie Treloar <[email protected]> wrote:
> On Thu, May 24, 2012 at 4:35 AM, Matt Veitas <[email protected]> wrote:
> > Recently the project I am working on ran into a very strange situation
> when
> > deploying a war file built with Maven where we were seeing values from
> the
> > pom.xml that was within the deployed war file replacing values in our jsp
> > files at runtime.
> [del]
> > Some of the JSP files in our project had values such as ${name} and
> ${url}
> > that were being replaced somehow at runtime with the values from the
> maven
> > pom file. I confirmed that the maven-war-plugin was not doing any
> > replacement of the jsp files.
>
> Do you have resource filtering turned on?
> http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
>
> To check you should run
> mvn help:effective-pom
> to ensure that this is not accidentally configured in the parent
> hierarchy somewhere
>
