M C wrote:
Hi Stephen,
Thanks for taking time to make a explanation of why the problem with naming and
co-existence. Things are clearer for me now.
Surely convincing the ruby developer world to add a "j" to all generated gem
tasks if running under jruby is a much bigger problem then just renaming the build-in
jruby commands I mentioned.
Maybe a pragmatic approach where we just renamed the bundled rake, spec, gem, ri scripts and
"forgot" about the remaining problem (just as ruby has been renamed to "jruby" and irb to
"jrib" in the distribution). At least this would mean that jruby as it is out-of-the-box will
co-exist perfectly without any hacks to the path.
Well, then you hit the whole problem with consistency. I know it's a
longer command line, but I've learned to live with doing -S for
everything I want. Especially since I have both rbx and ruby1.9 on the
system, it's not really a scalable approach to have different prefixes
for even these scripts.
Cheers
--
Ola Bini (http://ola-bini.blogspot.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
