[MNG-2339] ${project.*} are interpreted in the wrong place

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.4
• Fix Version/s: 2.0.9
• Component/s: General
• Assignee: Brett Porter
• Reporter: Emmanuel Venisse
• Created: 02/Jun/06 00:21
• Updated: 06/Apr/15 01:36
• Resolved: 29/Feb/08 00:54

Description

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

Issue Links

• is depended upon by: ARCHETYPE-78 Dependencies listed as version ${project.version} in maven-archetype prevent the use of archetypes
• is duplicated by: MNG-3009 Maven 2.0.5+ fails to resolve ${project.version} on deployment
• is duplicated by: MNG-2651 POM interpolator treats ${pom.something} like ${something} and prefers system properties
• is duplicated by: MNG-2653 using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)
• is duplicated by: MNG-2745 Do not allow System properties to be interpolated in the POM
• is duplicated by: MNG-2782 Version property in dependencies is not expanded correctly
• is related to: SUREFIRE-113 surefire-providers-2.0.pom contains strange dependencies which generate error