maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] (MNG-5185) Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
Date Sun, 05 Jan 2014 18:36:46 GMT


Jason van Zyl updated MNG-5185:

    Fix Version/s:     (was: 3.1.x)
> Improve "missing dependency" error message when _maven.repositories/_remote.repositories
contains other repository ids than requested
> -------------------------------------------------------------------------------------------------------------------------------------
>                 Key: MNG-5185
>                 URL:
>             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: 3.2
>         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|].
 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
> It would be good if Maven was updated with some improved error messages along the lines
> "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]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message