JRuby support about cassandra HOT 4 CLOSED

I'm not familiar enough with jruby to know how extensive problems like this are, but it seems to make sense to push this problem down the package management (echoe in this case). Do any of echoe's competitors do this better?

from cassandra.

I didn't know echoe has competitors :)

One idea that comes to mind is Bundler. We can can create a MRI and JRuby group marking the specific versions of 'json' we want or we can simply execute the statement some code to determine what version to use. Of course, Bundler comes with its own set of warts that can be annoying at times.

Jeweler and newgem appear to be in the same boat as echoe in this regard.

One of the ideas I bounced off Evan last week was the ability to pass a Proc (or string to eval) instead of a plain old string to the dependencies portion of the spec and then call the Proc from gemspec.

from cassandra.

After investigating this for more than a couple of hours, I really don't see a clean way to do this. I thought about adding a 'dependency_eval' stanza to Echoe that would simply be copied through to the .gemspec but all of the heavy lifting of generating the final .gemspec is handled by to_ruby in Gem::Specification.
At this point, I am considering using a Regex to rewrite %q{json} to my snippet above. Admittedly this is very hacky but unless we are willing to go the @wycats route by manually maintaining the .gemspec, I just don't see an easy, straightforward alternative.

from cassandra.

Yeah this is a total non-start at this point. I am just going to create a jruby branch for cassandra and cassandra_object and use Bundler to bring them in for my purposes.

I appreciate the consideration.

from cassandra.