cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject [Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
Date Thu, 28 Feb 2008 01:15:07 GMT
Eventually ...

Joerg

-------- Original Message --------
Subject: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the 
wrong place
Date: Wed, 27 Feb 2008 18:56:28 -0600 (CST)

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

Brett Porter closed MNG-2339.
-----------------------------

     Resolution: Fixed

> ${project.*} are interpreted in the wrong place
> -----------------------------------------------
>
>                 Key: MNG-2339
>                 URL: http://jira.codehaus.org/browse/MNG-2339
>             Project: Maven 2
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.4
>            Reporter: Emmanuel Venisse
>            Assignee: Brett Porter
>            Priority: Critical
>             Fix For: 2.0.9
>
>
> If a plugin use ${project.version}, this parameter is interpreted with the version of
the current project and not the plugin version. I think we have the same pb with dependencies
and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT, ${project.version}
used in the plugin will be interpreted as 1.0-SNAPSHOT instead of 2.0

Mime
View raw message