On Sun, 25 Jul 2004 11:37:37 -0700, matthew.hawthorne <[EMAIL PROTECTED]> wrote:
Martin Cooper wrote:
Anyway, since "it exists locally" (it was part of the Maven download, after all!), this shouldn't be an issue, right? Maven does keep going after that.
I'm not sure that Maven reporting that the file "exists" locally is correct. I may have created the file locally, started downloading it, then failed to finish the download.
Can you examine: C:\Documents and Settings\mcooper\.maven\repository\ velocity\jars\velocity-1.4-dev.jar
and confirm that it looks ok?
Aha! You're right, it wasn't OK, it was truncated. It appears that all of the ones that caused exceptions are in the same state.
Obviously, I can download all of these manually, but that kinda defeats the purpose of Maven, so it would be nice to know why this is happening, and fix my machine so that it doesn't...
BTW, I have no problem connecting and downloading these manually, so there must be some odd thing in my setup that's causing Maven to fail. Any ideas much appreciated!
I suspect that it has nothing to do with your setup. Perhaps ibiblio was temporarily overloaded, or something.
Try this -- delete the directory C:\Documents and Settings\mcooper\.maven\repository\velocity
And attempt to run it again.
Maybe Maven doesn't use the md5 files to ensure that jars that are found locally are valid.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
