Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 27 Jan 2014 11:59:58 -0600 (CST)
From: "Jason van Zyl (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.130827.1319409551250.810.1390845598804@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.130827.1319409551250@codehaus01.managed.contegix.com>
References: <JIRA.130827.1319409551250@codehaus01.managed.contegix.com>
Subject: [jira] (MNG-5185) Improve "missing dependency" error message when
 _maven.repositories/_remote.repositories contains other repository ids than
 requested
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-5185:
-------------------------------

    Fix Version/s:     (was: 3.2)
                   Issues to be reviewed for 4.x

> Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-5185
>                 URL: https://jira.codehaus.org/browse/MNG-5185
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>    Affects Versions: 3.0.2, 3.0.3, 3.0.4
>            Reporter: Mark Derricutt
>            Assignee: Olivier Lamy
>             Fix For: Issues to be reviewed for 4.x
>
>         Attachments: 0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch
>
>
> Based on a discussion on the users list [1], [Maven 3 has changed how it resolves artifacts from local repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].  Unfortunately, when "conflicts" arise (GAV is cached in local repo, but restricted to some repository ids, and actual POM has no matching repository id declared), Maven just tells the user that the artifact could not be resolved.
> This leads to confusion from users who find the .jar files in their local repository without knowing this restriction feature: they just get frustrated and complain that "maven sucks".
> It would be good if Maven was updated with some improved error messages along the lines of:
> "The (GAV) artifact was found in your local repository, but came from remote repository "xxx": either configure this in your pom with (insert sample XML block in error message), or in your "yyy" mirror."
> The "mirror" section of the error message should be included -if- the current ~/.m2/settings.xml declares a mirror.  By improving the messages here we can help the users move on to building software, rather than pulling out their hair :)
> [1] http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html


--
This message was sent by Atlassian JIRA
(v6.1.6#6162)