[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232920#action_232920
]
Jeff MAURY commented on MWAR-157:
---------------------------------
The issue is not related to webResources but to filters. The problem comes from
the fact that filters loading is delegated to shared-filtering that doesn't use
the project basedir but the current directory as of 1.0-beta-4
> 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'.
> {code:xml}
> <webResources>
> <resource>
> <!-- this is relative to the pom.xml directory -->
> <directory>myup-web/src/main/web-resources</directory>
> </resource>
> </webResources>
> {code}
--
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
