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 208279 - Find Occurences (Alt+F7) tries wrongly to modify the file
Summary: Find Occurences (Alt+F7) tries wrongly to modify the file
Status: RESOLVED DUPLICATE of bug 206134
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P1 normal (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-10 21:24 UTC by celsidor
Modified: 2012-02-13 12:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot of the problem (208.96 KB, image/jpeg)
2012-02-10 21:24 UTC, celsidor 		Details
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 celsidor 2012-02-10 21:24:25 UTC 
Created attachment 115611 [details]
screenshot of the problem

Hi,

I recently downloaded NetBeans for C++ 7.1 and found a very annoying issue.

Well, first of all, I'm using ClearCase as source version control tool. 

When I click on a symbol (like function name) and try to find all occurrences of it (Alt+F7) it prompts me that dialog asking me what to do (Hijack/Checkout Reserved or Checkout Unreserved) as it would modify the file! This is a problem... since I'm just asking to search (not to modify) any file!

Moreover, it asks me that for EVERY file that it finds on the search process... so  if that symbol is present on 10 files, it asks me 10 times the same thing (since files are under source control so all of them are read only).

This is a serious issue... I regret I uninstalled the old NB version... Maybe I will have to install it again until this issue is solved.

Could you please fix this quickly?

Many thanks!
Celso.
Comment 1 Vladimir Voskresensky 2012-02-13 12:00:40 UTC 
thanks for the report, it will be fixed in upcoming 7.1.1 patch

*** This bug has been marked as a duplicate of bug 206134 ***