maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anj (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml
Date Tue, 06 May 2008 15:51:24 GMT

    [ http://jira.codehaus.org/browse/MRESOURCES-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133710#action_133710
] 

anj747 edited comment on MRESOURCES-20 at 5/6/08 10:51 AM:
--------------------------------------------------------

I agree, this is an important issue. Thankyou Erik for the patch, it worked a treat.

However I had to spoof a local maven "release" of this plugin to allow me to release my dependent
project (~ shudder ~).

      was (Author: anj747):
    I agree, this is an important issue. Thankyou Erik for the patch, it worked a treat.

However I had to spoof a local maven "release" of this plugin to allow me to release my dependent
project (~shudder~).
  
> Filtering ${foo.file} evaluates to in full path to pom.xml
> ----------------------------------------------------------
>
>                 Key: MRESOURCES-20
>                 URL: http://jira.codehaus.org/browse/MRESOURCES-20
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Windows XP, Maven 2.0.2
>            Reporter: Martin Onis
>            Priority: Minor
>         Attachments: MRESOURCES-20.patch
>
>
> If an unresolved variable is encountered, the plugin simply does not replace the variable
in the target file.
> If this unresolved variable however ends in ".file}" it will evaluate to a file object
that targets the current pom. This results in the replacement being the complete path to that
pom (in the 2.1 version of the plugin this results in a ClassCastException).
> The workaround is, of course, not to filter the affected files. 
> Though this will not work if other variables in the affected files do need to be replaced.

-- 
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