> > It would be nice if the maven dependency page provided a link to the > repository that the dependency is available from. > > When maven is running, it knows (or can know) the location it obtained the > jar from, so would be able to encode this in the generated site. >
Not necessarily. If a given jar file is available locally, Maven doesn't reference your maven.repo.remote settings at all. > This has some issues though, so it might be simpler to just provide a > repository tag as a child to the dependency tag which uses ibiblio as the > default. > I like the current approach. We use several jars that are not available on Ibiblio. Encoding the repository to use for each jar would make writing the POM tedious. Also, if we change repositories, currently, only one setting -- the maven.repo.remote -- has to be changed > This would benefit users a lot I think. Save them hunting through the > sourceforge or apache mirror systems when ibiblio has the values [and is a > mirror for both] anyway. > Why are the users hunting for the jar files? By users do you mean developers or end-users? Anyway, one just has to look at the designated remote repositories. Your needs can be satisfied if dependencies page presents the URLs to the repositories being used by the project -- a slight variation to your original suggestion. > Hen > > Sri --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
