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.
Build: NetBeans IDE 6.5 Beta (Build 200808111757) VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-b33 OS: Windows XP, 5.1, x86 User Comments: dkaris: In the "Ruby Gems" dialog, I switched Ruby Platform from JRuby to my native (1.8.6-p114) ruby. dkaris: In the "Ruby Gems" dialog, I switched Ruby Platform from JRuby to my native (1.8.6-p114) ruby. Stacktrace: java.lang.AssertionError: gemManager is reloaded at org.netbeans.modules.ruby.platform.gems.GemPanel.notifyGemsUpdated(GemPanel.java:327) at org.netbeans.modules.ruby.platform.gems.GemPanel.access$4200(GemPanel.java:90) at org.netbeans.modules.ruby.platform.gems.GemPanel$4$1.run(GemPanel.java:1173) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
Created attachment 72158 [details] stacktrace
My ruby\bin directory contained a "gem.rb" but did not contain a "gem" or "gem.bat" file. I created "gem" as a copy of "gem.rb" and "gem.bat" as @ECHO OFF @"ruby.exe" "%~dpn0" %* This resolved the problem. Note also, that before this change, the "Ruby Platforms" dialog showed my Gem Tool as "null (1.2.0)"; after this change it showed "c:\ruby\bin\gem (1.2.0)"
This issue seems to have gone unnoticed, sorry about that and thanks for posting your solution. The platform manager indeed expects to find a gem executable, how did you you install RubyGems to your platform? Of course the platform manager should really display a warning rather than throwing an AE, but I assume this isn't a very common case (hence adjusting the priority).
The whole Ruby environment here is checked in to our source control system, we don't run an installer on individual machines. Except for Netbeans, there didn't need to be a gem.bat because we had Windows file associations set up for .rb to be run with ruby.exe. So, from the Windows command line, typing "gem" worked.
Ah, that clarifies it, thanks. Need to make handling of this kind of cases more robust.