One way of achieving this would be to put the properties files that need to be filtered in a folder and the non-filtered ones in another folder. These folders can then be configured for <filtering>true/false</filtering> accordingly.
Something along the lines of: <resource> <directory>src/main/filtered</directory> <filtering>true</filtering> </resource> <resource> <directory>src/main/unfiltered</directory> <filtering>false</filtering> </resource> -Olivier On Sat, 2008-07-05 at 16:21 +0200, Peter Horlock wrote: > Noone? > > Please, there must be someone able to answer this?! > > > Thanks, > > Peter > > 2008/7/3 Peter Horlock <[EMAIL PROTECTED]>: > > > Hi, > > > > I want to let Maven / the Resource plugin ( > > http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html > > ) > > > > parse my source code to replace {project.version} with the current version > > of the project as defined in the pom. > > This works great, but - in JSTL, as well as in OpenLazlo, ${variableName} > > is also a variable of the language itself - > > therefore, this leads to collisions - for example, one of our developers > > used a variable named ${parent} which then was filtered by Maven and booom > > the code was broken. Yada yada YAda! > > > > => Is there a way of telling Maven to JUST filter certain properties? I > > know I could tell it to just filter certain files, > > but > > a) a developer could then STILL use ${parent} as a variable in this very > > file > > b) whenever I wanted a new file to be filtered, I would have to add this > > file to the filter section... > > > > Thanks a lot folks, > > > > Peter > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
