[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233204#action_233204
]
Jeff MAURY commented on MWAR-157:
-
No, 1.0-beta-4 did not fix the issue, it is even worse, it breaks the it tests
(one is failing due to the fact that the \ handling in resources is not handled
the same way between 1.0-beta-2 and 1.0-beta-4).
I agree with you that this should be done in filtering I have open an issue, I
will link this one with the filtering issue
> 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
> Attachments: patch157.patch
>
>
> 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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233137#action_233137
]
Dennis Lundberg commented on MWAR-157:
--
So did 1.0-beta-4 solve the issue?
I would prefer that we try to fix this in maven-filtering, if possible.
> 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
> Attachments: patch157.patch
>
>
> 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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232998#action_232998
]
Jeff MAURY commented on MWAR-157:
-
Forget about my comment regarding maven-filtering, I just tried by 1.0-beta-4
to see if this shoud fix the problem but the patch I submitted has been
validated with 1.0-beta-2 (pom not modified)
> 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
> Attachments: patch157.patch
>
>
> 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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232987#action_232987
]
Dennis Lundberg commented on MWAR-157:
--
But the current version of Maven WAR Plugin uses maven-filtering 1.0-beta-2,
not 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
> Attachments: patch157.patch
>
>
> 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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231761#action_231761
]
Dennis Lundberg commented on MWAR-157:
--
Can someone provide a sample project for this?
The value use for the resource directory smells to me. Is myup-web a module in
the multi module setup?
> 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}
>
>
>
> myup-web/src/main/web-resources
>
>
> {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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[
http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184647#action_184647
]
Sylvain FRANCOIS commented on MWAR-157:
---
One workaround is to use {{$\{project.basedir\}}} :
{code:xml}
${project.basedir}/myup-web/src/main/web-resources
{code}
> 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'.
>
>
>
> myup-web/src/main/web-resources
>
>
--
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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[ http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184629#action_184629 ] Sylvain FRANCOIS commented on MWAR-157: --- Same with Maven 2.0.9 and maven-war-plugin 2.1-alpha-1 > 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'. > > > > myup-web/src/main/web-resources > > -- 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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[ 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 org.apache.maven.plugins maven-war-plugin 2.1-beta-1 src/main/resources_DEV/filter.web.xml.properties true 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'. > > > > myup-web/src/main/web-resources > > -- 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
[jira] Commented: (MWAR-157) webResources paths NOT resolved relative to pom.xml but relative to 'current directory'
[ http://jira.codehaus.org/browse/MWAR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135134#action_135134 ] koen handekyn commented on MWAR-157: Maven version: 2.0.9 Java version: 1.5.0_12 OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows" > 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'. > > > > myup-web/src/main/web-resources > > -- 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
