[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171064#action_171064
]
Greg almond commented on MWAR-157:
----------------------------------
I have the similar issue with filters.
My application is layered in two levels. The first level contains the parent
pom, the second level a web module
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
<configuration>
<filters>
<filter>src/main/resources_DEV/filter.web.xml.properties</filter>
</filters>
<filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
</configuration>
The filter is found if the Maven command is run from within the web module..
But the filter is not found when the maven command is run from the parent
project.
> webResources paths NOT resolved relative to pom.xml but relative to 'current
> directory'
> ---------------------------------------------------------------------------------------
>
> Key: MWAR-157
> URL: http://jira.codehaus.org/browse/MWAR-157
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: windows
> Reporter: koen handekyn
>
> in the documentation it is stated that directories are relative to the
> pom.xml which is how it should be indeed.
> however, the runtime behaviour is that webResources directories are resolved
> relative to the 'current working directory'.
> <webResources>
> <resource>
> <!-- this is relative to the pom.xml directory -->
> <directory>myup-web/src/main/web-resources</directory>
> </resource>
> </webResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
