Maven gives up looking for parent pom

[David Jackman <Da...@fastsearch.com>]

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.
 
Obviously, this is some sort of bug somewhere.  Has anyone seen this and
has it already been reported?  If not, where do I go from here (i.e.
where would I report this and what additional reproduction information
would you need)?
 
..David..
 

Re: [m2] Maven gives up looking for parent pom

[takai <da...@aperto.de>]

David,

if you'd like you could report it in Codehaus' jira:

http://jira.codehaus.org/browse/MNG

Cheers,
Daniel


David Jackman wrote:
> 
> 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.
>  
> Obviously, this is some sort of bug somewhere.  Has anyone seen this and
> has it already been reported?  If not, where do I go from here (i.e.
> where would I report this and what additional reproduction information
> would you need)?
>  
> ..David..
>  
> 
> 

-- 
View this message in context: http://www.nabble.com/Maven-gives-up-looking-for-parent-pom-tf3309863s177.html#a9269663
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org