JRuby 1.0.3 broken gem install

I’m stuck trying to do what I’m doing in a Java 1.4 environment. That
being said, I’m trying to use jruby-1.0.3.

It’s failing out of the box to do any gem installs right now…

$ jruby -v
ruby 1.8.5 (2007-12-15 rev 5200) [i386-jruby1.0.3]

$ 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


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

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 :slight_smile:


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Ray K. wrote:

Am I just screwed? Is jruby-1.0.3 end-of-life at this point?
Thanks :slight_smile:

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.

  • Charlie

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

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 :slight_smile:


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

On 10 Nov, 2008, at 4:10 PM, Ray K. wrote:

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 :slight_smile:

If you haven’t already, you could try pointing out that it’s been EOL’d.


Bill K.


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

If you haven’t already, you could try pointing out that it’s been EOL’d.

Oracle Java Technologies | Oracle

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.

No worries, another day, another challenge :slight_smile:


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Ray K. wrote:

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 :slight_smile:

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