This sounds a lot like a problem I was seeing. I haven't have very much time to investigate, but it appears as though Maven gets to the first repository and it does have an entry for the groupId and artifactId, but not the particular version of the artifact. However, instead of going on to the other repositories, Maven just gives up and says it can't find it. Could that be what you're seeing as well?
..David.. -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 8:46 PM To: Maven Users List Subject: Re: M2 Repository Resolution On 5/17/07, Morgovsky, Alexander (US - Glen Mills) <[EMAIL PROTECTED]> wrote: > I define three repositories, but when the build does not find the > dependency in the first repository, the build fails. Specifically, the > build does not proceed to search the other two repositories for the > dependency. Why could this be? Thanks. Sorry, there isn't enough information here to help... Where/how did you define the repositories? What command did you execute, and what is the exact error message? It's probably not relevant to this problem but it never hurts to tell us what version you're using. :) If you can get on irc (#maven on codehaus, there's a web interface here: http://irc.codehaus.org/) we can probably sort it out fairly quickly. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
