that's certainly a bug to report under the MEV JIRA project - you can find details on the web site of how to do that.
I would suggest using dependency management to force the 2.0.6 version in the mean time. On 27/06/07, iamamaven <[EMAIL PROTECTED]> wrote:
The metadata file for spring is showing 2.0-m4 as the latest availble: http://repo1.maven.org/maven2/org/springframework/spring/maven-metadata.xml But the directory is showing more versions available (I'm trying to get 2.0.6): http://repo1.maven.org/maven2/org/springframework/spring/ I can get this version by specifying it directly, but I would like to use a version range like this: [2.0,) I get this message back: Couldn't find a version in [1.0, 1.0-m4, 1.0-rc1, 1.1, 1.1-rc1, 1.1-rc2, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.2, 1.2-rc1, 1.2-rc2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 2.0-m2, 2.0-m4] to match range [2.0,) org.springframework:spring-null.jar Is there something wrong with the metadata file or am I confused. Using maven 2.0.6 Thanks, -- View this message in context: http://www.nabble.com/missing-metadata-on-repo1.maven.org--tf3984897s177.html#a11314146 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
