commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <>
Subject [jira] Closed: (CONFIGURATION-435) Timestamp version in repository for commons configuration
Date Fri, 11 Feb 2011 14:30:58 GMT


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:
>             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.
> 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 (
> Best regards,

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message