$ jruby -S gem install activerecord
Bulk updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem … (NativeException)
org.jvyamlb.ParserException: ParserException while scanning a
block mapping we had this expected , but found
org.jvyamlb.tokens.ScalarToken
ERROR: While executing gem … (NativeException)
org.jvyamlb.ParserException: ParserException while scanning a
block mapping we had this expected , but found
org.jvyamlb.tokens.ScalarToken
OK, I’ve tried this now on Windows and Ubuntu, under JDK 1.4 and 1.5.
jruby-1.0.3 is just plain busted it seems. I figured maybe rubygems
needed to be updated, but that fails too…
$ jruby -S gem update --system
Updating RubyGems…
Bulk updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem … (NativeException)
org.jvyamlb.ParserException: ParserException while scanning a
block mapping we had this expected , but found
org.jvyamlb.tokens.ScalarToken
I even went so far as to hack my jruby.jar and drop the org.jvyamlib
package and add the latest stand-alone version of that to my
classpath. No luck.
Am I just screwed? Is jruby-1.0.3 end-of-life at this point?
Thanks
Am I just screwed? Is jruby-1.0.3 end-of-life at this point?
Thanks
Well here’s the deal…we have nowhere near enough people to continue
making changes/updates to the 1.0 line, so as far as current resources
1.0 is EOL. That said, we’re not opposed to applying patches or giving
commit rights to 1.0 branch if there are people who want to keep it
alive.
Well here’s the deal…we have nowhere near enough people to continue making
changes/updates to the 1.0 line, so as far as current resources 1.0 is EOL.
That said, we’re not opposed to applying patches or giving commit rights to
1.0 branch if there are people who want to keep it alive.
Thanks. I think I’ll just kick and scream that we need to get the hell
off of JDK 1.4 around here
Well here’s the deal…we have nowhere near enough people to
continue making
changes/updates to the 1.0 line, so as far as current resources 1.0
is EOL.
That said, we’re not opposed to applying patches or giving commit
rights to
1.0 branch if there are people who want to keep it alive.
Thanks. I think I’ll just kick and scream that we need to get the hell
off of JDK 1.4 around here
If you haven’t already, you could try pointing out that it’s been EOL’d.
Oh I have…
But with old-ass-weblogic comes old-ass-java. We’re making the changes
needed to get off that junk. I wanted to get us going using
ActiveRecord migrations asap though as I yapped about here…
Unfortunately getting jruby-1.1 going involves getting jdk 1.5
installed which sort of negates my main reason for using JRuby. I was
hoping to avoid a full “software install” by just dropping jruby on
the box. If I gotta have our ops folks install jdk 1.5, I might as
well have them install MRI if we’re going to go installing stuff.
Unfortunately getting jruby-1.1 going involves getting jdk 1.5
installed which sort of negates my main reason for using JRuby. I was
hoping to avoid a full “software install” by just dropping jruby on
the box. If I gotta have our ops folks install jdk 1.5, I might as
well have them install MRI if we’re going to go installing stuff.
No worries, another day, another challenge
I have no idea whether it works, but you could also try retroweaving
JRuby to Java 1.4.
Charlie
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.