Bug 101805 – GTK LF only: unable to install any module on Gem Manager

HOME / Community

Bug 101805 - GTK LF only: unable to install any module on Gem Manager

Summary:

GTK LF only: unable to install any module on Gem Manager

Status:	RESOLVED FIXED

Product:	ruby
Component:	Code
Version:	6.0
Platform:	Sun Solaris

Priority:	P2 (vote)
Target Milestone:	6.0
Assigned To:	Torbjorn Norbye
QA Contact:	issues@ruby

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-04-19 16:06 by Masaki Katakai
Modified:	2007-07-03 14:44 (History)

Issue Type:	DEFECT
Exception Reporter :

Attachments
exception (6.43 KB, application/octet-stream) 2007-04-19 16:08, Masaki Katakai	Details
View All 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 From Masaki Katakai 2007-04-19 16:06:33

It seems that this exception happens on only GTK L&F.

I'm using NB6.0 M8 + Ruby Pack on Solaris Nevada build 62 and JDK6u1. By
default, NetBeans starts in native GTK L&F but it fails when I try to install
module on Gem Manager

1. Start NB
2. Tools -> Ruby Gem Manager
3. Click Install New
4. Select a module
5. Click Install 

It always happens.

When I tried Swing L&F, this problem does not happen. Should we report this
to JDK side? Any workaround in NB?

    at
org.netbeans.modules.ruby.rubyproject.gems.InstallationSettingsPanel.getName(InstallationSettingsPanel.java:68)
    at com.sun.java.swing.plaf.gtk.GTKStyle.getInsets(GTKStyle.java:263)
    at javax.swing.plaf.synth.SynthStyle.installDefaults(SynthStyle.java:876)

....

------- Comment #1 From Masaki Katakai 2007-04-19 16:08:34 -------

Created an attachment (id=41265) [details]
exception

------- Comment #2 From Torbjorn Norbye 2007-04-19 20:11:39 -------

Fixed. The method getName() in InstallationSettingsPanel was accidentally
overriding a method in a 
superclass, and that method appears to be used during initialization in GTK -
not in the other L&F's.

------- Comment #3 From Masaki Katakai 2007-04-19 23:52:30 -------

Thank you very much for quick fixing!! I'll try to verify the fix at M9.

------- Comment #4 From Jiri Kovalsky 2007-07-03 14:01:32 -------

Reassigning this issue to newly created 'ruby' component.

------- Comment #5 From Jiri Kovalsky 2007-07-03 14:44:10 -------

Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1
build.