You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2005/12/20 16:02:35 UTC

[jira] Moved: (MRESOURCES-3) When filtering, ${java.version} gets replaced with pom.version instead.

     [ http://jira.codehaus.org/browse/MRESOURCES-3?page=all ]

Vincent Massol moved MNG-1193 to MRESOURCES-3:
----------------------------------------------

    Fix Version:     (was: 2.0.1)
      Component:     (was: Inheritence and Interpolation)
                     (was: maven-resources-plugin)
       Workflow: jira  (was: Maven)
            Key: MRESOURCES-3  (was: MNG-1193)
        Project: Maven 2.x Resources Plugin  (was: Maven 2)

> When filtering, ${java.version} gets replaced with pom.version instead.
> -----------------------------------------------------------------------
>
>          Key: MRESOURCES-3
>          URL: http://jira.codehaus.org/browse/MRESOURCES-3
>      Project: Maven 2.x Resources Plugin
>         Type: Bug

>     Reporter: David Jackman
>     Assignee: Kenney Westerhof

>
>
> When filtering, the resources plugin should be using the system property value, but is getting mixed up and using the value from the pom instead.  I'm told the same confusion is happening with ${pom.organization.name} getting replaced with pom.name.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org