Hello!
On Thu, May 20, 2010 at 8:26 PM, Antoine T.
[email protected] wrote:
Hi guys,
we are trying to figure a way to get Buildr out of the door.
First, it looks like we have failures with JRuby 1.4.1 on Windows 7:
[BUILDR-443] Spec failures while running with JRuby on Windows 7 - ASF JIRA
=> Could you take a look at the file attached and see if those errors are
fixed in 1.5 ?
There’s about 43 of them, yeah? Have they ever passed? I didn’t scroll
through the whole list of failures (it was very long).
Second, we cannot run with JRuby 1.5 (this happens on Mac or Windows 7):
[BUILDR-441] Support for JRuby 1.5 - ASF JIRA
which points to:
[BUILDR-418] jruby exception: `ffi_libraries': no library specified - ASF JIRA
=> Anybody with FFI knowledge I can chat with on that ?
Wayne covered this. However if I set it to always explicitly load C
library, I get the following now, perhaps with newer RubyGems (not
sure if this affects RubyGems 1.3.6 or just 1.3.7 which we now have on
master:
~/projects/jruby âž” jruby -rubygems -e “p Gem::Requirement::OP_RE”
-e:1: uninitialized constant Gem::Requirement::OP_RE (NameError)
That shows up here in Buildr:
~/projects/jruby/minitwitter âž” buildr
/Users/headius/projects/jruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2503:in
`const_missing’: uninitialized constant Gem::Requirement::OP_RE
(NameError)
from
/Users/headius/projects/jruby/lib/ruby/gems/1.8/gems/buildr-1.3.5-java/lib/buildr/packaging/version_requirement.rb:24
Not sure what you’re using that for or if it affects 1.5.
[BUILDR-442] Errors while running the specs with jruby 1.5 - ASF JIRA
=> Did you guys make changes to Rake, by monkey-patching it or enhancing it
? This error is weird.
I don’t believe so, and in fact we install rake from a stock gem
during our build. The specific Ant support isn’t loaded unless you
require ‘ant’…maybe we have a library name conflict?
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email