[
http://jira.codehaus.org/browse/MRESOURCES-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125530
]
Olivier Lamy commented on MRESOURCES-35:
----------------------------------------
In my mind "All file references are always relative to the project itself."
But why not.as a resource directory can be now an absolute path.
> targetPath doesn't accept absolute paths
> ----------------------------------------
>
> Key: MRESOURCES-35
> URL: http://jira.codehaus.org/browse/MRESOURCES-35
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: linux, windows
> Reporter: Paul Jungwirth
> Priority: Minor
> Fix For: 2.3
>
> Attachments: absolute-resource-outputs.patch
>
>
> <targetPath> is always relative to target/classes, even if you pass it an
> absolute path. This happens if the path is from a variable, like this:
> <targetPath>${basedir}/scripts</targetPath>
> It also happens if you write the path directly:
> <targetPath>/home/pjungwir/src/encc/scripts</targetPath>
> or on windows:
> <targetPath>C:/home/pjungwir/src/encc/scripts</targetPath>
> Your resources wind up in directories like this:
> /home/pjungwir/src/encc/target/classes/home/pjungwir/src/encc/scripts
--
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
