OK, I have a work around that I think will work for me.
I add a properties section to my pom and copy the values I want from my
project and from my profile respectively into new property names.
The war plugin picks these up no problem.
<properties>
<my.artifactId>${project.artifactId}</my.artifactId>
<my.version>${project.version}</my.version>
<my.jndi.name>${jndi.name}</my.jndi.name>
This approach works for versions 2.0, 2.0.2 of the maven-war-plugin
Chris Barran wrote:
Dear maven users,
I cannot get the maven-war-plugin filtering to work as expected.
I'm trying to configure my context.xml thus.
<Context path="/${pom.artifactId}-${pom.version}"
docBase="${pom.artifactId}-${pom.version}">
<ResourceLink name="${jndi.name}" global="${jndi.name}"/>
</Context>
${jndi.name} can configured in a properties file or in a profile or an
the command line.
I can get the jndi.name property to replace for plugin version 2.0
I can get the pom.* properties to work for version 2.0.1+ but not both
what is going on?
I can't find the answer in the docs or mail archive.
Others seem to report the problem and get no answer
Others claim it's fixed.
This seems to have come up repeatedly for 2 to 3 years. Other folks
must be using some work around.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
