[
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
