Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 11 Feb 2011 14:18:57 +0000 (UTC)
From: "Andres Gomez Casanova (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <1822694585.10522.1297433937461.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (CONFIGURATION-435) Timestamp version in repository
 for commons configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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