Re: [Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
Joerg Heinicke pisze: Eventually ... Joerg Yep... But can we start to think about pushing minimal version require for working with Cocoon? I know that 2.0.9 is not released yet but it looks like Maven folks are planning the release already. I'm very motivated to remove all these crap MNG-2339 introduced to our POMs. -- Best regards, Grzegorz Kossakowski
Re: [Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
On 07.03.2008 17:41, Grzegorz Kossakowski wrote: Yep... But can we start to think about pushing minimal version require for working with Cocoon? I know that 2.0.9 is not released yet but it looks like Maven folks are planning the release already. I'm very motivated to remove all these crap MNG-2339 introduced to our POMs. Can you describe what the current situation is? I thought we have problems only when using Java 1.4. You are talking about fixes to our POMs because of this issue. In which cases exactly do they apply and why not in the other ones? Are they only for Java 5 or has Java 5 never been a problem? Depending on the answer to the last question we could just recommend (i.e. not enforce) either use Maven 2.0.9 or Java 5. If removing all the crap breaks Cocoon with Java 5 as well I definitely prefer to raise the minimal required Maven version. If not I'm fine either way. Joerg
[Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
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
