[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299771#comment-299771
]
Tim Molter commented on MNG-5185:
---------------------------------
Improving this error message would be a very quick change and would save people
like me literally hours of frustration. I'm sure this issue turns people away
from Maven. I blogged about this issue here:
http://obscuredclarity.blogspot.com/2012/05/using-maven-offline.html, in hopes
other people will find the solution faster. Improving this error message is a
no-brainer.
> 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
>
> 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
