[jira] (MNG-5185) Improve "missing dependency" error message when _maven.repositories conflict

["Devin Reid (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305575#comment-305575 ] 

Devin Reid commented on MNG-5185:
---------------------------------

Just got bit by this one. I have using '-Dmaven.repo.local' option to create portable builds for working on non-networked (default settings.xml on those boxes) computers and spent about an hour scratching my head as to why this didn't work with Maven3. After deleting all the _maven.repositories it finally worked. This new 'feature' really introduces some headaches for certain uses of maven3. 

So +1 for improving the error message.

bonus points if this feature could be disabled for offline "mvn -o" builds entirely.
                
> Improve "missing dependency" error message when _maven.repositories conflict
> ----------------------------------------------------------------------------
>
>                 Key: MNG-5185
>                 URL: https://jira.codehaus.org/browse/MNG-5185
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>            Reporter: Mark Derricutt
>         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 of:
> "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] http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira