Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <18797121.32321251102701560.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Mon, 24 Aug 2009 03:31:41 -0500 (CDT)
From: "Benjamin Bentmann (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Created: (MNG-4317) [regression] g:a level metadata is not
 properly processed when resolving plugin version
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

[regression] g:a level metadata is not properly processed when resolving plugin version
---------------------------------------------------------------------------------------

                 Key: MNG-4317
                 URL: http://jira.codehaus.org/browse/MNG-4317
             Project: Maven 2
          Issue Type: Bug
          Components: Artifacts and Repositories, Plugins and Lifecycle
    Affects Versions: 3.0-alpha-3
            Reporter: Benjamin Bentmann


I recently observed trunk to fail resolving a version for plugin although the plugin was present (even locally). Some debugging showed it merely picked the first existing metadata file (which was almost empty) and didn't consider/merge the metadata of other repos.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira