You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Jackman (JIRA)" <ji...@codehaus.org> on 2007/03/05 19:17:00 UTC
[jira] Created: (MNG-2858) Maven isn't looking in all repositories
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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "David Jackman (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100104 ]
Brian Fox commented on MNG-2858:
--------------------------------
I think I've seen this too. Will try to reproduce it.
> 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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "Barrett Nuzum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92560 ]
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: 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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "David Jackman (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100169 ]
David Jackman commented on MNG-2858:
------------------------------------
Thanks for taking another look. I did another test and it appears as though if a repository has one version of the artifact but not the requested version, Maven doesn't look in the other repositories for the correct version. I wanted to do a more controlled test to prove that this was the problem, but I haven't had the time to do it.
If you find the time to try this out, please add a comment here. If I somehow find the time to try this (it's on a very long list of things to do, and not doing this item won't get me fired), I'll post a comment.
> 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
> Assignee: Brian Fox
>
> 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
[jira] Closed: (MNG-2858) Maven isn't looking in all repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-2858.
-----------------------------
Resolution: Incomplete
Fix Version/s: (was: Reviewed Pending Version Assignment)
we need more information to reproduce this, as stated... hasn't gotten a response since.
> 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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92528 ]
Wendy Smoak commented on MNG-2858:
----------------------------------
Related thread: http://www.nabble.com/What%27s-the-deal-with-MNG-2858--%21--t3555869.html
> 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
[jira] Commented: (MNG-2858) Maven isn't looking in all
repositories
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92512 ]
Carlos Sanchez commented on MNG-2858:
-------------------------------------
no sample, no test, no output, this doesn't make it easy to reproduce
> 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