You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Maik Ebert (JIRA)" <ji...@apache.org> on 2012/09/25 08:27:07 UTC
[jira] [Created] (CONFIGURATION-509) Maven central
maven-metadata.xml contains only a small subset of available versions
Maik Ebert created CONFIGURATION-509:
----------------------------------------
Summary: 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
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 (we using version fixed [1.6]) Maven thinks 1.6 is not available on Maven central and does not download it.
Our build fails. We are not able to build.
--
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
[jira] [Resolved] (CONFIGURATION-509) Maven central
maven-metadata.xml contains only a small subset of available versions
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CONFIGURATION-509) Maven central
maven-metadata.xml contains only a small subset of available versions
Posted by "Maik Ebert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maik Ebert updated CONFIGURATION-509:
-------------------------------------
Description:
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.
was:
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 (we using version fixed [1.6]) Maven thinks 1.6 is not available on Maven central and does not download it.
Our build fails. We are not able to build.
> 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
[jira] [Commented] (CONFIGURATION-509) Maven central
maven-metadata.xml contains only a small subset of available versions
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463166#comment-13463166 ]
Oliver Heger commented on CONFIGURATION-509:
--------------------------------------------
Do we have a Maven hero on this list who knows a solution directly or should I ask on repository@?
Out of curiosity: Is there a specific reason why you stick to version 1.6? Meanwhile 1.9 is available which is binary compatible and should contain lots of improvements and bug fixes.
> 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
[jira] [Closed] (CONFIGURATION-509) Maven central
maven-metadata.xml contains only a small subset of available versions
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger closed CONFIGURATION-509.
--------------------------------------
> 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