maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barrett Nuzum (JIRA)" <>
Subject [jira] Commented: (MNG-2858) Maven isn't looking in all repositories
Date Wed, 11 Apr 2007 14:36:46 GMT


Barrett Nuzum commented on MNG-2858:

We dealt with a similar issue --
We found we had to be using 'deploy' to the internal repository.
'install' does not create the metadata required for Maven to find the artifact.
Are you using deploy?

> Maven isn't looking in all repositories
> ---------------------------------------
>                 Key: MNG-2858
>                 URL:
>             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:
For more information on JIRA, see:


View raw message