Firstly, -o won't work, because I have to re-enable it everytime a build fails for a legitimate dependency.
Secondly, it's snapshots built from dev source code - I update via SVN and build them to get the latest versions. So they're not available in the remote repositories yet. And it's definitely required dependencies. It's getting bad, because as the project grows, they get more, and I wait about 40 seconds now just for the downloads to fail, so my build can complete. Quintin Beukes On Fri, Oct 2, 2009 at 8:43 PM, Brian Fox <[email protected]> wrote: > On Fri, Oct 2, 2009 at 3:54 AM, Quintin Beukes <[email protected]> wrote: >> Hey, >> >> Whenever a project depends on a snapshot versioned library, then it >> tries to update this snapshot. If the snapshot isn't found in any of >> the repositories, then it obviously doesn't update. But now it tries >> again with the next build. And over, and over, and over. > > I'll ask the obvious question first: Why do you have a dependency that > doesn't exist? And if your build succeeds without this dependency, is > it even a defacto dependency? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
