You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/06/25 22:55:28 UTC

[jira] Closed: (MNG-3535) Valid properties which look self referential fail to resolve

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

John Casey closed MNG-3535.
---------------------------

    Resolution: Fixed

> Valid properties which look self referential fail to resolve
> ------------------------------------------------------------
>
>                 Key: MNG-3535
>                 URL: http://jira.codehaus.org/browse/MNG-3535
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.9
>            Reporter: Chris Custine
>            Assignee: John Casey
>             Fix For: 2.0.10
>
>         Attachments: model-int.patch
>
>
> In 2.0.9 properties which look self referential but would otherwise resolve to a system property are failing due to fixes for MNG-2339.  Current example is any version of jruby shared pom at 
> http://repo1.maven.org/maven2/org/jruby/shared/1.0.1/shared-1.0.1.pom
> which contains:
> <java.specification.version>${java.specification.version}</java.specification.version>
> The question is whether this should be valid or not, but it has worked in every version up to and including 2.0.8 because System properties were available in the first interpolate step.  In 2.0.9 this first pass does not include the system props and an exception is thrown because of the self reference check.

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