maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff MAURY (JIRA)" <>
Subject [jira] (MNG-5185) Improve "missing dependency" error message when _maven.repositories conflict
Date Fri, 01 Feb 2013 12:38:13 GMT


Jeff MAURY commented on MNG-5185:

The main problem with this "feature" is that it is not documented thus I
can't explain the real reason why Maven download several times released
artifacts and this causes members of the Maven bashing group to grow

> Improve "missing dependency" error message when _maven.repositories conflict
> ----------------------------------------------------------------------------
>                 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.1.0
>         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 custom repositories.  Unfortunately, when conflicts arise ( GAV is in local repo, but
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,
and 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
> "The {GAV} artifact was found in your local repository, but came from the undeclared
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:!default.jspa
For more information on JIRA, see:


View raw message