You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Andres Gomez Casanova (JIRA)" <ji...@apache.org> on 2011/02/11 15:18:57 UTC
[jira] Created: (CONFIGURATION-435) Timestamp version in repository
for commons configuration
Timestamp version in repository for commons configuration
---------------------------------------------------------
Key: CONFIGURATION-435
URL: https://issues.apache.org/jira/browse/CONFIGURATION-435
Project: Commons Configuration
Issue Type: Bug
Components: Build
Environment: Any,
Reporter: Andres Gomez Casanova
Hi
I'm using "Maven Version plugin" with an option that updates the release to the newest one, actually with this option 'mvn versions:use-next-releases' or 'mvn versions:display-dependency-updates'.
However, there is a deployed version of your plugin (commons configuration) in 2004, and the other plugin thinks that is the newest version.
I took a look in the Maven repository and I found that.
http://mvnrepository.com/artifact/commons-configuration/commons-configuration
There is a possibility to undeploy these old releases (2003 and 2004). I think there are just alpha versions, because you history release starts after there releases (http://commons.apache.org/configuration/changes-report.html)
Best regards,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONFIGURATION-435) Timestamp version in repository
for commons configuration
Posted by "Joerg Schaible (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Schaible closed CONFIGURATION-435.
----------------------------------------
Resolution: Invalid
Commons configuration has nothing to do with the maven versions plugin. If that plugin is not capable to sort out such SNAPSHOT releases that report it as bug of the plugin. And note that the central Maven repository is read-only. We cannot even change this even if we would.
> Timestamp version in repository for commons configuration
> ---------------------------------------------------------
>
> Key: CONFIGURATION-435
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-435
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Environment: Any,
> Reporter: Andres Gomez Casanova
> Labels: alpha, maven, old, repository, version
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Hi
> I'm using "Maven Version plugin" with an option that updates the release to the newest one, actually with this option 'mvn versions:use-next-releases' or 'mvn versions:display-dependency-updates'.
> However, there is a deployed version of your plugin (commons configuration) in 2004, and the other plugin thinks that is the newest version.
> I took a look in the Maven repository and I found that.
> http://mvnrepository.com/artifact/commons-configuration/commons-configuration
> There is a possibility to undeploy these old releases (2003 and 2004). I think there are just alpha versions, because you history release starts after there releases (http://commons.apache.org/configuration/changes-report.html)
> Best regards,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONFIGURATION-435) Timestamp version in
repository for commons configuration
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995080#comment-12995080 ]
Sebb commented on CONFIGURATION-435:
------------------------------------
Sorry, it was actually https://issues.sonatype.org/browse/MVNCENTRAL-45 - which has now been fixed.
> Timestamp version in repository for commons configuration
> ---------------------------------------------------------
>
> Key: CONFIGURATION-435
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-435
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Environment: Any,
> Reporter: Andres Gomez Casanova
> Labels: alpha, maven, old, repository, version
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Hi
> I'm using "Maven Version plugin" with an option that updates the release to the newest one, actually with this option 'mvn versions:use-next-releases' or 'mvn versions:display-dependency-updates'.
> However, there is a deployed version of your plugin (commons configuration) in 2004, and the other plugin thinks that is the newest version.
> I took a look in the Maven repository and I found that.
> http://mvnrepository.com/artifact/commons-configuration/commons-configuration
> There is a possibility to undeploy these old releases (2003 and 2004). I think there are just alpha versions, because you history release starts after there releases (http://commons.apache.org/configuration/changes-report.html)
> Best regards,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONFIGURATION-435) Timestamp version in
repository for commons configuration
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993564#comment-12993564 ]
Sebb commented on CONFIGURATION-435:
------------------------------------
There appears to be a problem in the maven-metadata.xml file - for some reason, that does not list any releases after 1.2,
It ought to have been updated with 1.3,...,1.6 as they were added but was not for some reason.
I think this is something that can be fixed, but not by Commons - it is a Maven issue.
I'll see if I can find the correct place to request that this be fixed.
> Timestamp version in repository for commons configuration
> ---------------------------------------------------------
>
> Key: CONFIGURATION-435
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-435
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Environment: Any,
> Reporter: Andres Gomez Casanova
> Labels: alpha, maven, old, repository, version
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Hi
> I'm using "Maven Version plugin" with an option that updates the release to the newest one, actually with this option 'mvn versions:use-next-releases' or 'mvn versions:display-dependency-updates'.
> However, there is a deployed version of your plugin (commons configuration) in 2004, and the other plugin thinks that is the newest version.
> I took a look in the Maven repository and I found that.
> http://mvnrepository.com/artifact/commons-configuration/commons-configuration
> There is a possibility to undeploy these old releases (2003 and 2004). I think there are just alpha versions, because you history release starts after there releases (http://commons.apache.org/configuration/changes-report.html)
> Best regards,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONFIGURATION-435) Timestamp version in
repository for commons configuration
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993568#comment-12993568 ]
Sebb commented on CONFIGURATION-435:
------------------------------------
Created https://issues.sonatype.org/browse/MVNCENTRAL-4 which I hope is the correct place to report such matters.
> Timestamp version in repository for commons configuration
> ---------------------------------------------------------
>
> Key: CONFIGURATION-435
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-435
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Environment: Any,
> Reporter: Andres Gomez Casanova
> Labels: alpha, maven, old, repository, version
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Hi
> I'm using "Maven Version plugin" with an option that updates the release to the newest one, actually with this option 'mvn versions:use-next-releases' or 'mvn versions:display-dependency-updates'.
> However, there is a deployed version of your plugin (commons configuration) in 2004, and the other plugin thinks that is the newest version.
> I took a look in the Maven repository and I found that.
> http://mvnrepository.com/artifact/commons-configuration/commons-configuration
> There is a possibility to undeploy these old releases (2003 and 2004). I think there are just alpha versions, because you history release starts after there releases (http://commons.apache.org/configuration/changes-report.html)
> Best regards,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira