maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MSHARED-66) targetPath doesn't accept absolute paths
Date Fri, 12 Sep 2008 21:03:48 GMT

     [ http://jira.codehaus.org/browse/MSHARED-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivier Lamy updated MSHARED-66:
--------------------------------

       Assignee: Olivier Lamy
    Component/s: maven-filtering

> targetPath doesn't accept absolute paths
> ----------------------------------------
>
>                 Key: MSHARED-66
>                 URL: http://jira.codehaus.org/browse/MSHARED-66
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-filtering
>    Affects Versions: maven-filtering-1.0-beta-1
>         Environment: linux, windows
>            Reporter: Paul Jungwirth
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: maven-filtering-1.0-beta-2
>
>         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

        

Mime
View raw message