> Tried again, got the right ant-optional. Current maven > wouldn't build (test failure, I think), but that's ok.
Yeah, I noticed that. Changelog plugin doesn't build "offline" or behind a firewall. I'll put it in JIRA. > So, questions: > 1) Why the corrupt dependency? How do I prevent this in the > future? It seems like once you have a broken jar in your > local repository, you're screwed. Also seems like if you > have two projects getting the "same" dependency from > different sites, it will only get the first one. Could be > wrong here, love to know. I've seen this before. There's some preliminary md5 support in Maven. If that were enforced, then the deps can be validated. As for only getting the first one, this is the expected behaviour, unless they are SNAPSHOTs in which case the newest one is downloaded. > 2) How does a compilation error and a failed build result in > a successful build? I can paste the log, but it's rather long. I think it is to do with Maven return codes. Feel free to file an issue in JIRA. You don't need to pass in the whole compilation, just the relevant part of the bootstrap and a snippet of the error message (eg was it building the plugins, installing the plugins, building maven with itself?) > 3) Does it seem odd to anyone else that compilation occurs > under a "clean-maven-home" task? It just looks that way. Its not actually occurring in that task. Glad you got it going! Cheers, Brett
