[
http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92510
]
David Jackman commented on MNG-2858:
------------------------------------
I need to boost the priority of this bug. This error is occurring again and
again for people in my development group and is starting to hinder the
migration of our projects to Maven 2.
If I had a clue where to look for the problem I would fix it myself. The
workaround is not scalable across the entire organization.
> Maven isn't looking in all repositories
> ---------------------------------------
>
> Key: MNG-2858
> URL: http://jira.codehaus.org/browse/MNG-2858
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: David Jackman
>
> I've created a settings.xml that lists all of our internal repositories (some
> Maven 1, some Maven 2). One of these repositories contains the parent POM
> for the project I'm trying to build. However, Maven reports that it can't
> "locate resource in repository" and lists all of the repositories in
> settings.xml.
>
> Looking at the debug output, it seems like Maven is only looking for the
> parent pom in the first of the repositories in this list (the one just after
> central). The correct repository is the second one in the list.
>
> To test this theory, I removed the repository it was having problems with
> from settings.xml. Sure enough, Maven found the parent pom just fine. I
> also changed the ID of the repository in settings.xml (which changes its
> position in the list--must be a HashMap or something) and it found the parent
> pom just fine in this situation, too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
