Invalid version numbers in commons-beanutils
--------------------------------------------
Key: MEV-464
URL: http://jira.codehaus.org/browse/MEV-464
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid POM
Reporter: Paul Wills
The maven2 repository for commons-beanutils has the following versions.
<versions>
<version>1.0</version>
<version>1.0-dev.20020812.082103</version>
<version>1.0-dev.20020913.114846</version>
<version>1.2</version>
<version>1.3</version>
<version>1.4</version>
<version>1.4-dev</version>
<version>1.4-dev.20020812.084325</version>
<version>1.4.1</version>
<version>1.5</version>
<version>1.6</version>
<version>1.6-dev.20021128.082114</version>
<version>1.6.1</version>
<version>1.7-dev</version>
<version>1.7.0</version>
<version>20020520</version>
<version>20021128.082114</version>
<version>20030211.134440</version>
<version>dev</version>
</versions>
I believe the version numbers that begin with the year are invalid and it
causes the following problem.
The problem I have is when another module registers its dependence on a
particular version of beanutils, for example
<version>[1.4,)</version>
then maven2 will attempt to download the most recent version with the highest
major and minor version number. So it always chooses 20030211.134440 as the
correct version to compile with.
All of the invalid version number POM's need to be renamed
--
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
