On Tue, Sep 2, 2008 at 12:41 PM, Tammo van Lessen <[EMAIL PROTECTED]> wrote: > Hi guys, > > we've been struggling lately with buildr and particularly in conjunction > with Ode's build. > > I'm not sure whether this belongs more to [EMAIL PROTECTED] or [EMAIL > PROTECTED], but as > the communities are quite overlapping I think this one is okay. > > So here are our observations, I'll write them in a list. For few of them > are probably no answers cooked yet, I'll start with them ;) > > The environment is winxp, java 5+6, ruby 1.8.6 > > - buildr/ruby consumes about 100% CPU when downloading dependencies!?
I'm guessing the progress bar. Can you open an issue for this? > - when running junit test in buildr's default fork mode, we get multiple > OOMs, looks like something leaks memory. With :fork=>each it works quite > good. The default mode forks once per project, running all tests from that project in a single VM. The VM would have Ant, JUnit, JMock, and any code/dependencies specific to that project. So the most likely suspect is shared state that the tests are not cleaning up after they run. (If it's not forking, however, then you get all of Buildr/javac/etc crowding the same memory space) > - when buildr runs with TEST=all, it sometimes completely ignores test > cases (my gut feeling is that it ignores build failures and continues > without executing them, which is quite obvious) TEST=all tells Buildr to swallow all exceptions produced during the test run, maybe it's swallowing too many. Worth opening an issue for this, change it and see if things improve. It doesn't swallow any build failures. > - buildr eclipse ignores project that do not contain java related > package tasks. This results in skipping the bpel-script project that is > though depended by other project in eclipse. The same appears in the > extensions project, which is basically a wrapper project for our > extensions. So a buildr eclipse in Ode's top level directory ignores the > extensions directory and therefore also skips the extension projects. > - buildr eclipse does not work with buildr 1.3.2 (undefined to_sym). > This has been fixed in buildr trunk, but buildr trunk does not work with > Ode's rakefile (the Release class extension, which is anyways quite > mysterious for me ;)) In particular we wonder if buildr has a concept > for achieving backward compatibility. Not documented, I'll write something about that, but basically point releases should not break public APIs/behavior without good reason. Assaf > > I hope this can help the buildr crowd a bit and last but not least our > (Ode's) build system :) > > Cheers, > Tammo >
