On Fri, 8 Aug 2003 12:30 pm, [EMAIL PROTECTED] wrote: > Yep, that'd be nice, but maven can't know where all possible jar files are > stored. The only place it can look is on the remote repo. It does say > where its trying to download it from, and the only place to stick it is > the local repo.
Maven itself can't know about all jars, but the developers who make the dependencies know. I suggest that (a) maven get a feature which allows it to retrieve from the repository information about an undownloadable jar, and (b) developers who depend on such jars put such information in the repository. All it has to be is a short note saying "Sun does not allow this jar to be distributed automatically. Please go to this page to get it." Of course, no rush, I would like to see some bugs fixed first, but this would be a whole lot nicer than "no such jar aaaarrrgggh.' > > What if I find an archive of xsdlib nightly builds, but > > it only goes back 3 months? > That's what the project info dependencies page is for. See > http://jakarta.apache.org/commons/jelly/libs/swing/dependencies.html for > an example. Good point, but xsdlib is not listed there. The xsdlib I can download is 20030225, although the dependency is on 20020414. How does the project dependencies page get to be wrong anyway? Isn't it generated from the same stuff that makes me need it? BTW, how does Maven depend on jelly when jelly is in such a sorry state? Is there an internal release which is not available to the public at large? John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
