[
https://issues.apache.org/jira/browse/CONFIGURATION-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-509.
----------------------------------------
Resolution: Fixed
Thanks to infra this issue has been fixed now. The metadata file in Maven
central now again contains all released versions.
Thanks for the report.
> Maven central maven-metadata.xml contains only a small subset of available
> versions
> -----------------------------------------------------------------------------------
>
> Key: CONFIGURATION-509
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-509
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Reporter: Maik Ebert
> Labels: maven
>
> When Maven tries to find out the available versions of commons-configuration
> on Maven central it downloads
> http://repo1.maven.org/maven2//commons-configuration/commons-configuration/maven-metadata.xml
> Problem is that this file does only contain a subset of available versions:
> {noformat}
> <metadata
> modelVersion="1.1.0"><groupId>commons-configuration</groupId><artifactId>commons-configuration</artifactId><versioning><latest>1.9</latest><release>1.9</release><versions><version>1.7</version><version>1.8</version><version>1.9</version></versions><lastUpdated>20120821191916</lastUpdated></versioning></metadata>
> {noformat}
> So in our case Maven thinks 1.6 is not available on Maven central and does
> not download it.
> Our build fails. We are not able to build.
> Please correct the list of versions on Maven central in the above
> maven-metadata.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
