I've updated the build guide for the test and eclipse problems. The version problem though is a bit trickier. We'll have to see how we can solve that without requiring a double install of buildr or you having to check the actual version to install in the Rakefile.
Matthieu On 5/31/07, Rich Taylor <[EMAIL PROTECTED]> wrote:
Oh...beautiful. And you're right, the eclipse projects do actually work out of the box. As for moving to buildr, what I ran into is: - After installing builr using "gem install buildr" it installed buildr version 1.1.2. But when I ran "rake package" in the Ode trunk it said something about a wrong version and I had to change my local Rakefile to say " gem "buildr", "1.1.2" ". Which probably isn't the right approach but it's working for the moment. - When tyring to build, tests failed and I had to dig for a while to find out about "test=off" - It wasn't clear that "rake eclipse" was available, nor that it's output was better than the Maven approach. That could be used as a selling point. Overall it was fairly painless and it does seem faster. I would suggest putting notes about some of the above items right on the "Building Ode" page. They might ease the transition for others. Rich On 5/31/07, Alex Boisvert <[EMAIL PROTECTED]> wrote: > > On 5/31/07, Rich Taylor <[EMAIL PROTECTED]> wrote: > > > > On a side note I've been trying to move to buildr as well. I'm not sure > > yet > > if there is a way to create an Eclipse project from buildr (don't think > > so). So I've still been using Maven for that. > > > > 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. > > BTW, if you have/had any pain transitioning to buildr, we'd love to hear > about it! > > alex >
