Details
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
-
-
MNG-2651
POM interpolator treats ${pom.something} like ${something} and prefers system properties
-
-
MNG-2653
using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)
-
-
MNG-2745
Do not allow System properties to be interpolated in the POM
-
-
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
-