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 8844 - File system search is not working in build 1099j
Summary: File system search is not working in build 1099j
Status: CLOSED FIXED
Alias: None
Product: utilities
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: PC Windows 3.1/NT
: P4 normal (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-08 20:53 UTC by bburch
Modified: 2003-07-01 15:31 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 bburch 2000-12-08 20:53:12 UTC 
FFJ 2.0 Internet Edition Build 1099J (EAP download).

Edit->Search File Sytems->Full Text tab->Substring radio button

This search type is not working for me, get an exception dialog right away
that says a java.lang.IncompatibleClassChangeError exception has occurred.
Comment 1 Tomas Pavek 2000-12-13 16:23:59 UTC 
Do you have imported some older project settings? If yes, from what IDE version?
Please try to delete all "Full Text" nodes in Project Settings -> Search Types
and create a new one (only one). Does it solve the problem?
Comment 2 bburch 2000-12-14 20:06:59 UTC 
In response to tomas.pavek:

No older project settings. Completely un-installed previous Forte and deleted
all old directories. Did a complete, fresh install of 1099j and downloaded ALL
updates.

Deleted all nodes under Project Settings -> Search Types and added back a
single node for Full Text Service.

Same bug still exists.

The IDE version? Are you asking for the Forte version or a module version? The
Forte version is Forte for Java, release 2.0, Internet Edition, build 1099j. If
you are asking for some other version, please clarify.
Comment 3 Peter Zavadsky 2001-03-16 08:00:05 UTC 
This doesn't appear in [release32] and [main-trunk] too. So I close the issue.
Comment 4 pfelenda 2003-04-22 17:56:38 UTC 
Verified. This issue doesn't appear in newer version. (tested since
release32)
Comment 5 Quality Engineering 2003-07-01 15:31:31 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.