Problems with bundle update

Ruby JRuby
1

When I run bundle update I receive this error:

Using polyglot (0.3.1)
Using treetop (1.4.9)
Using mail (2.2.19)
Using actionmailer (3.0.7)
System.java:-2:in arraycopy': java.lang.ArrayIndexOutOfBoundsException from DefaultResolver.java:111:inmakeTime’
from DefaultResolver.java:277:in create' from DefaultResolver.java:317:inhandleScalar’
from DefaultResolver.java:435:in orgHandler' from DefaultResolver.java:455:innode_import’
from DefaultResolver$s$1$0$node_import.gen:65535:in call' from CachingCallSite.java:137:incall’

etc…

There is some way to solve it?

2

I have the same issue. Charles said it’s a YAML bug that’s fixed in
the Jruby1_6 branch on github. I haven’t been able to confirm yet.

3

On 20 May 2011 13:06, Marlon M. [email protected] wrote:

I have the same issue. Charles said it’s a YAML bug that’s fixed in
the Jruby1_6 branch on github. I haven’t been able to confirm yet.

So how can it be solved?
I’m stopped because of this problem.

4

On May 20, 2011, at 9:10 AM, Mauro wrote:

On 20 May 2011 13:06, Marlon M. [email protected] wrote:

I have the same issue. Charles said it’s a YAML bug that’s fixed in
the Jruby1_6 branch on github. I haven’t been able to confirm yet.

So how can it be solved?
I’m stopped because of this problem.

I was able to reproduce your error locally and the simplest solution is
to run bundle update under 1.9:

jruby --1.9 -S bundle update

Alternatively, you could add a dependency on arel version 2.0.9 to your
Gemfile since 2.0.10 is what’s triggering the issue.

Ben

5

On 20 May 2011 13:49, Benjamin B. [email protected] wrote:

I was able to reproduce your error locally and the simplest solution is to run
bundle update under 1.9:

jruby --1.9 -S bundle update

yes it works I don’t use 1.9 by default because I know some gems
aren’t not compatible with 1.9.

6

build from github I guess.

Charles said 1.6.2 would be coming out soon, but he didn’t give an exact
date.

sorry! Luckily I was just testing my app with jruby so I was able to
switch back to MRI 1.9.2.

7

On 20 May 2011 15:14, Nick S. [email protected] wrote:

Have a look at http://bugs.jruby.org/5581. It’s probably related. We’ll have
1.6.2 out soon.

I use jruby --1.9 -S bundle update for now.

8

Have a look at http://bugs.jruby.org/5581. It’s probably related. We’ll
have 1.6.2 out soon.

/Nick

9

On Fri, May 20, 2011 at 2:35 PM, Mauro [email protected] wrote:

undefined method `task’

I’m using also rails_config gem and with jruby1.9 I have the error
“unitialized constant Settings”.
With jruby --1.8 I had no problems.
I think that ruby 1.9 support is not complete.

I can confirm this behavior as well. When we released 1.6.1 this was
not happening so a subsequent Rails release must have uncovered a bug
in our 1.9 support. This will be fixed for 1.6.2, but we need to
understand why first (of course).

-Tom

–
blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

10

On 20 May 2011 13:49, Benjamin B. [email protected] wrote:

I was able to reproduce your error locally and the simplest solution is to run
bundle update under 1.9:

jruby --1.9 -S bundle update

If I run jruby --1-9 it installs gems for 1.9.
Now I have to use jruby --1.9 also for my applications but they don’t
work anymore.
For example rake cucumber says:

rake aborted!
undefined method `task’

I’m using also rails_config gem and with jruby1.9 I have the error
“unitialized constant Settings”.
With jruby --1.8 I had no problems.
I think that ruby 1.9 support is not complete.