On Thu, May 24, 2012 at 9:01 AM, Matt Veitas <[email protected]> wrote: > 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.
Another thought is to grep every file and look for the keys that are being replaced. I suspect it may be <exploded.war>/maven/<groupId>/<artifactId>pom.properties If you can find all the files with those keys, and then "fiddle" with the values to determine which file is causing the problem that might help you with extra google queries or questions to mailing lists. I don't do a lot of web development so I can't offer any more advice. Someone else might have bright ideas. It may also be specific to you web container. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
