>> What I'm seeing, regardless of packaging type, is if you explicitly >> configure this plugin, it won't expand ANY properties within the file.
I doubt this is what is going on. Lots of people use filters with various configurations applied. >> For grins, I took the same file I wanted to filter, put it in >> src/main/resources, added a <resources> stanza and boom - everything is >> properly filtered. This just tells me that your original configuration did not properly define the resource you were wanting to filter, so Maven could not find it, so it did not filter it. Did you try <include>**/foo.txt</include>? Tell us what else you did try so far. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
