> -----Original Message----- > From: Vikas Phonsa [mailto:[EMAIL PROTECTED] > Sent: Friday, October 17, 2003 2:55 PM > To: 'Maven Users List' > Subject: RE: Getting dependencies from mulitple repositories > > Sri, > > What's the difference between the <url> element in the <dependency> and > the > URLs that we give to maven.repo.remote.
The url element that is part of the dependency fragment is simply for documentation purposes. For example, if you have a dependency on log4j, you might want to specify the <url> as http://jakarta.apache.org/log4j. Then, when you generate your project's web site, the dependencies' page will show this helpful link. (For details see http://maven.apache.org/reference/project-descriptor.html#dependencies. Although I do see a confusing statement at this site that says " This url will be provided to the user if the jar file cannot be downloaded from the central repository" -- don't know what *that* means) So you see this has nothing to do with *how* Maven gets log4j. That is the role of the maven.repo.remote property. > > If I set the maven.repo.remote URLs to the Maven repositories where my jar > could be found, then would Maven like search one URL after another to find > the dependency jars. Yes. > > Does the <url> specified in a dependency serve as the location to search > for > jars if they can't be found from maven.repo.remote > No > > Thanks again > > Vikas Sri --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
