Ola Bini wrote:
Current trunk is broken with regards to gem install. It's 6448 or 6449
that's the culprit.
Ok, I fixed the problems with arity as well. For any cases where there
were two methods on a given Java impl of the same name, since it
generated the handle class name based on only expl
Charles Oliver Nutter wrote:
Ola Bini wrote:
Vladimir Sizikov wrote:
Charlie,
It seems that the recent changes are also causing two rubyspec
regressions:
http://pastie.org/178534
# jruby -e "p Process::GID.eid"
# -e:1: wrong # of arguments(0 for 1) (ArgumentError)
Thanks,
--Vladimir
Ola Bini wrote:
Vladimir Sizikov wrote:
Charlie,
It seems that the recent changes are also causing two rubyspec
regressions:
http://pastie.org/178534
# jruby -e "p Process::GID.eid"
# -e:1: wrong # of arguments(0 for 1) (ArgumentError)
Thanks,
--Vladimir
And building AR-JDBC from tru
Vladimir Sizikov wrote:
Charlie,
It seems that the recent changes are also causing two rubyspec regressions:
http://pastie.org/178534
# jruby -e "p Process::GID.eid"
# -e:1: wrong # of arguments(0 for 1) (ArgumentError)
Thanks,
--Vladimir
And building AR-JDBC from trunk also breaks with
Charlie,
It seems that the recent changes are also causing two rubyspec regressions:
http://pastie.org/178534
# jruby -e "p Process::GID.eid"
# -e:1: wrong # of arguments(0 for 1) (ArgumentError)
Thanks,
--Vladimir
On Thu, Apr 10, 2008 at 2:34 PM, Charles Oliver Nutter
<[EMAIL PROTECTED]> wr
Ola Bini wrote:
Current trunk is broken with regards to gem install. It's 6448 or 6449
that's the culprit.
Fixed and added a test for it. BasicSocket.do_not_reverse_lookup= was
incorrectly named "set_do_not_reverse_lookup". gems install fine now.
- Charlie
--
Current trunk is broken with regards to gem install. It's 6448 or 6449
that's the culprit.
--
Ola Bini (http://ola-bini.blogspot.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yi
