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 188470 - Regression: Opening Projects from 6.9 in 6.9.1 resets the ruby environment from Native Ruby to JRuby
Summary: Regression: Opening Projects from 6.9 in 6.9.1 resets the ruby environment fr...
Status: REOPENED
Alias: None
Product: ruby
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 normal (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 05:34 UTC by esmithbss
Modified: 2011-01-28 20:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-07-08 05:34:32 UTC 
Product Version = NetBeans IDE 6.9.1 Dev (Build 201006282301)
Operating System = Linux version 2.6.32-23-generic running on i386
Java; VM; Vendor = 1.6.0_20
Runtime = Java HotSpot(TM) Client VM 16.3-b01

When an existing Rails project from NetBeans 6.9 is loaded into NetBeans 6.9.1, it resets the Ruby Platform from the native ruby environment to the built-in JRuby-1.5.1.  This wreaks havoc with projects configured to use gems within the native environment without significant warnings.  The first indication the user receives is an exception thrown during a generate, a server launch, or script execution.
Comment 1 Erno Mononen 2010-07-08 07:24:39 UTC 
Seems to be a duplicate of 187422, the same problem with 6.9 too. There's an issue with the platform detection, for some reason some platforms don't get always detected even when on the path, so the IDE resorts to the built-in platform even for projects set to use MRI. The workaround is, as you probably know, to manually configure the platforms again. (Or let me know if the MRI platform was automatically detected but not used by the IDE, in that case this would be a different issue).

*** This bug has been marked as a duplicate of bug 187422 ***
Comment 2 esmithbss 2010-07-08 18:24:52 UTC 
Either the platform was properly detected and ignored, or he platform was identified when the project was opened and identified by NB at that point.

My first reaction when seeing that the problem was a gem issue was to go to the Gems dialog and look at the installed gems.  Both the built-in JRuby and the MRI were listed.

I then switched to the project where I noticed the project settings were wrong.
Comment 3 Erno Mononen 2010-07-12 06:54:22 UTC 
I see, I'll need to try a few different scenarios to see if I can reproduce this. If not, I'll add some extra logging for tracking this down.
Comment 4 Erno Mononen 2010-07-12 08:08:16 UTC 
Changing this to a P2 as per the priority guidelines (while the issue is unfortunate there is a reasonable straightforward workaround).