I have filtering set up in my pom.xml like this:
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
<includes>
<include>**/*.*</include>
</includes>
</directory>
</resource
</resources>
</build>
(I've done this many many many many times before.)
Inside src/main/resources/META-INF I have placed a file called test.crap:
Hello, ${project.artifactId}!
Sure enough, mvn clean process-resources causes
target/classes/META-INF/test.crap to contain:
Hello, foobar!
...where my project's artifact name is (let's say) foobar. All fine
and good and exactly as I'd expect.
Next, I took the real file I'm trying (unsuccessfully) to filter
(ra.xml). I placed it alongside test.crap in
src/main/resources/META-INF and replaced a single bit of text with
${project.artifactId}.
At the end of the filtering run, test.crap is, again, filtered
successfully. ra.xml is not (the ${project.artifactId} reference
remains in the target/classes/META-INF/ra.xml version.
Is there something special about an ra.xml file that causes
maven-resources-plugin not to filter it (surely not)? Or XML files in
general? Or...?
Best,
Laird
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
