Hello-
I've created a properties file and refer to it in a <filter> element. The
properties are referenced in a web.xml file via ${} parameters.
By using the following setup, I get a web.xml that has the parameters replaced:
<filters>
<filter>webApp.properties</filter>
</filters>
<resources>
<resource>
<directory>src/main/webapp/WEB-INF</directory>
<filtering>true</filtering>
<includes>
<include>web.xml</include>
</includes>
</resource>
</resources>
But the generated web.xml file goes to the target/classes folder, whereas I
want it to go to the target/<warfile>/WEB-INF folder.
If I add the following:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<configuration>
<phase>package</phase>
<outputDirectory>target/${project.build.finalName}/WEB-INF</outputDirectory>
</configuration>
</plugin>
It looks like the generated web.xml gets clobbered by the original web.xml in
src.
Someone here just now suggested modifying the war plugin config to pull web.xml
from the target/classes folder instead of src. Sounds workable. Any other
ideas?
-- Jeff
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
