Hi,
sorry Tamo, but kind of cools me down to hear that. I was struggling
with buildr for almost two entire days on a Mac 10.5, java 5, ruby 1.8.6
- buildr fails to load some dependencies (solved by adding more
repositories)
- tests fail but, oddly enough, not always the same tests (but always
the HttpBindingTest)
- had the to_sym error as well which lead to building buildr-trunk
from sources:
- started withour warnings, ended in compiling java libraries until
all memory was used by rake
- installed scala and jruby manually (found that somewhere)
- modified lib/buildr/java.rb because there is no tools.jar in non-sun-
sdks like Apples or IBMs etc
- finally build buildr (without passing the tests though)
- buildr now gives another error: undefined method `tag' for class
`Class'
- well I'm quite new to buildr and ruby and I have really no idea what
this means but commenting out line 181 in the buildfile cuts it
- finally created eclipse project
- with buildr-trunk some other tests fail, incl HttpBindingTest
- and the same thing with some subprojects in eclipse...
For me its quite oddly or random that not always the same tests fail
(albeit failing right after checkout).
Maybe my experiences help somewhere as well.
--Matthias
Am 02.09.2008 um 21:41 schrieb Tammo van Lessen:
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!?
- 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.
- 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)
- 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.
I hope this can help the buildr crowd a bit and last but not least our
(Ode's) build system :)
Cheers,
Tammo
