I just updated the Rakefile to work against any 1.1.x version of Buildr ( 1.1.1, 1.1.2, etc).
I recommend upgrading to 1.1.2, which should fix the download problem you're seeing above, apparently a keep-alive bug with the Maven repo. Assaf On 5/31/07, Jim Alateras <[EMAIL PROTECTED]> wrote:
> Simply run "rake eclipse" from the trunk's root. Bonus: it generates > Eclipse projects that are ready to use. No more manual tweaking for the > generated classes. > Did do that and i'm getting the following C:\projects\ode\ode>rake eclipse test=no (in C:/projects/ode/ode) Downloading clover:clover:jar:1.3.11 Downloading http://repo1.maven.org/maven2/clover/clover/1.3.11/clover-1.3.11.jar 100% |.........................................| 1.5MB/ 1.5MB Time: 00:00:24 end of file reached rake aborted! Failed to download clover:clover:jar:1.3.11, tried the following repositories: http://pxe.intalio.org/public/maven2 http://people.apache.org/repo/m2-incubating-repository http://repo1.maven.org/maven2 http://people.apache.org/repo/m2-snapshot-repository (See full trace by running task with --trace) C:\projects\ode\ode> > BTW, if you have/had any pain transitioning to buildr, we'd love to hear > about it! so far buildr itself has been fine. cheers </jima> BTW I was at a ruby\rails user group last night and buildr got an honorable mention.
