maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MAVEN-1688) The ${pom.versions} List behaves differently when running plugins under maven 1.1 and maven 1.0
Date Sun, 11 Mar 2007 19:49:34 GMT

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

Lukas Theussl updated MAVEN-1688:
---------------------------------

    Fix Version/s:     (was: 1.1-rc1)

> The ${pom.versions} List behaves differently when running plugins under maven 1.1 and
maven 1.0
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAVEN-1688
>                 URL: http://jira.codehaus.org/browse/MAVEN-1688
>             Project: Maven 1.x
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1-beta-2
>            Reporter: Henning Schmiedehausen
>
> Consider the following POM snipped:
> <versions>
>     <version>
>       <name>2.1</name>
>       <tag>TURBINE_2_1</tag>
>     </version>
>     <version>
>       <name>2.2</name>
>       <tag>TURBINE_2_2_0</tag>
>     </version>
>     <version>
>       <name>2.3-rc1</name>
>       <tag>TURBINE_2_3_RC1</tag>
>     </version>
>     <version>
>       <name>2.3-rc2</name>
>       <tag>TURBINE_2_3_RC2</tag>
>     </version>
>     <version>
>       <name>2.3</name>
>       <tag>TURBINE_2_3</tag>
>     </version>
>     <version>
>       <name>2.3.1-RC1</name>
>       <tag>TURBINE_2_3_1_RC1</tag>
>     </version>
>     <version>
>       <name>2.3.1-RC2</name>
>       <tag>TURBINE_2_3_1_RC2</tag>
>     </version>
>     <version>
>       <name>2.3.1</name>
>       <tag>TURBINE_2_3_1</tag>
>       <id>2.3.1</id>
>     </version>
>     <version>
>       <name>2.3.2-RC1</name>
>       <tag>TURBINE_2_3_2_RC1</tag>
>     </version>
>   </versions>
> echoing ${pom.versions} under the 1.0.2 maven release issues the following output:
>     [echo] [2.1, 2.2, 2.3-rc1, 2.3-rc2, 2.3, 2.3.1-RC1, 2.3.1-RC2, 2.3.1, 2.3.2-RC1]
> doing the same thing under the 1.1-beta 2 core results in
>     [echo] [null, null, null, null, null, null, null, 2.3.1, null]
> It seems that 1.0 uses the name as key and 1.1 uses the id. This causes e.g. the clirr
plugin to fail if a project
> defines names for a version entry but no id.
> If it is necessary that a version entry contains name and/or id, it should be enforced
by the maven core and bad
> entries should be reported.

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

        

Mime
View raw message