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 252227 - Go to Type -> UnsupportedOperationException: CASE_INSENSITIVE_CAMEL_CASE
Summary: Go to Type -> UnsupportedOperationException: CASE_INSENSITIVE_CAMEL_CASE
Status: REOPENED
Alias: None
Product: ruby
Classification: Unclassified
Component: Navigation (show other bugs)
Version: 8.1
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-04 10:53 UTC by NukemBy
Modified: 2015-05-06 10:03 UTC (History)
0 users

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 NukemBy 2015-05-04 10:53:46 UTC
I feel that problem appeared in NB 2-3 weeks ago (as i can't remember it happening to me before).

Steps to reproduce:

1. Invoke "Navigate -> Go to Type" (no matter from menu or via shortcut)

2. An exception dialog pops up 

"Unexpected Exception: A org.openide.util.RequestProcessor$SlowItem exception has occurred." ... 

3. Click "Review and Report Problem" -> NB generates summary string "UnsupportedOperationException: CASE_INSENSITIVE_CAMEL_CASE"


This happens for each invocation of "Go to type" and is really annoying. Currently using NetBeans IDE Dev (Build 201505010001). Please fix.
Comment 1 Marian Mirilovic 2015-05-06 07:22:37 UTC
Please attach the whole messages.log file - or much better just report it directly through Exceptions Reporter (use "Review & Report" button in Exceptions dialog)
Comment 2 NukemBy 2015-05-06 09:23:36 UTC
I've already reported it via Exception Reporter several times - i see the first one is from 2015-04-22
http://statistics.netbeans.org/analytics/detail.do?id=216905
Comment 3 NukemBy 2015-05-06 10:03:18 UTC
Looked into exception report - it seems like problem comes from ruby staff. I have ruby plugin installed, but it was inactive. Problem disappeared after uninstall of  ruby plugin. I expect inactive plugin should also cause no problems ...

Changed product/component to ruby/navigation.