[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Walton updated MNG-5185:
-------------------------------
Attachment:
0001-MNG-5185-Warn-about-artifacts-present-but-not-available-eclipse-aether.patch
bq. This patch will have to be adapted and integrated into an Aether 1.0 before
we absorb it.
I've updated the patch to apply against the Eclipse aether-core master branch.
This gets more complicated now Aether and Maven are separate projects: is this
a useful change? What would the next steps be to get this into an Eclipse
release that Maven could then consume?
> 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-available-eclipse-aether.patch,
> 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)
