This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 105747 - Possible to set Ruby/JRuby interpreter by command option
Summary: Possible to set Ruby/JRuby interpreter by command option
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-05 15:22 UTC by Petr Blaha
Modified: 2007-07-03 14:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Blaha 2007-06-05 15:22:34 UTC
In the latest NB builds the JRuby/Ruby interpreter has to be selected when a
project is created first time in IDE with clean userdir. However, we need to set
interpreter outside of our automated tests. Is it possible to create new command
line option when we can set JRuby interpreter for IDE instance? In this case
Select interpreter dialog should not be visible.
Comment 1 Torbjorn Norbye 2007-06-05 18:15:41 UTC
I already have such a flag;
 -J-Druby.interpreter=/Users/tor/dev/ruby/install/ruby-1.8.5/bin/ruby

I haven't tested if this suppresses the choose ruby interpreter dialog (because the dialog only shows if you 
have native Ruby in your $PATH, and on the Mac I don't (the /usr/bin/ruby isn't good enough so is 
specifically ignored on the Mac).

If it's showing the dialog let me know and I'll turn that off when ruby.interpreter is set.
Comment 2 Petr Blaha 2007-06-12 13:29:27 UTC
Thanks Tor, the option works fine. When you set the option then the dialog isn't opened. There is just small issue that
you don't check the path whether includes ruby interpreter. I was able to set
Users/tor/dev/ruby/install/ruby-1.8.5/bin/ruby in my laptop but the interpreter isn't really in this path. This is P4
and should be tracked in different issue.
Comment 3 Jiri Kovalsky 2007-07-03 13:57:44 UTC
Reassigning this issue to newly created 'ruby' component.
Comment 4 Jiri Kovalsky 2007-07-03 14:41:49 UTC
Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1 build.