Compatibility with jRuby about resque-status HOT 4 CLOSED

I'm not sure how familiar the resque-status dev is with JRuby so I got this in front of some JRuby eyes. They recommended trying a more recent version. It looks like you're using rvm which has the latest version, JRuby 1.6.5 available for installation. I primarily recommend this because 1.6.5 has many bug fixes in it.

from resque-status.

My initial guess at this would be a contention between Rake and JRuby import statements. I would not be surprised if the code runs fine outside of rake and blows up like this while trying to run the tests. I don't see any import statements in the resque-status codebase so I imagine that it is in one of it's dependencies.

from resque-status.

Ok, so i did a bit of digging and I think I figured this out. resque-status has a dependency on uuid. uuid has a dep on macaddr, which has a dep on systemu. systemu contains a jruby specific block that uses the jruby import statement. The jruby import clashes with the rake import. I think the jruby community advocates moving to the java_import statement instead to deal with issues like this but the import is still left in for backward compatibility.

Anyway. I made the mod to a fork of systemu in my github account and started using that for a project that I have that uses resque-status and I can now run tests under jruby without the typical cant convert Class to String explosion going on. I have a pull req into the owner of systemu so hopefully it will make it in there sometime in the future.

from resque-status.

Since this seems to be a downstream problem with JRuby/Systemu/uuid closing this ticket.

from resque-status.