commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-435) Timestamp version in repository for commons configuration
Date Fri, 11 Feb 2011 16:37:57 GMT


Sebb commented on CONFIGURATION-435:

Created which I hope is the correct place
to report such matters.

> 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