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 155624 - problems with rename + IDE frozen
Summary: problems with rename + IDE frozen
Status: VERIFIED DUPLICATE of bug 151787
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-17 08:33 UTC by unr303
Modified: 2009-04-28 12:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log file when netbeans get frozen (14.66 KB, application/x-gzip)
2008-12-17 08:34 UTC, unr303
Details
screenshot (340.02 KB, image/jpeg)
2008-12-17 08:35 UTC, unr303
Details
gestures when netbeans get frozen (12.61 KB, application/x-gzip)
2008-12-17 08:37 UTC, unr303
Details

Note You need to log in before you can comment on or make changes to this bug.
Description unr303 2008-12-17 08:33:44 UTC
1 create new repository
2 check it out
3 create project in working copy
4 add 2 classes, one uses another
5 commit
6 refactor/rename class that is used by another
7 change anything in that class
8 hit "save all"
9 get error messages
10 revert all changes from outside of netbeans
11 get back to netbeans
12 it gets frozen

Changed made after refactor/rename get lost in any case (even if you dont revert).

Happened two times and was able to reproduce it third time.
Comment 1 unr303 2008-12-17 08:34:44 UTC
Created attachment 75069 [details]
log file when netbeans get frozen
Comment 2 unr303 2008-12-17 08:35:52 UTC
Created attachment 75070 [details]
screenshot
Comment 3 unr303 2008-12-17 08:37:57 UTC
Created attachment 75071 [details]
gestures when netbeans get frozen
Comment 4 Tomas Stupka 2008-12-17 10:44:47 UTC
looking at the error messages you got in 9.) it seems like this is related with issue #151787 which was fixed after 6.5
and is scheduled as a candidate for the next patch release. We also wasn't able to reproduce on a trunk build, so the
guess is your problem is an after effect of the bug reported in #151787. For now i'm setting this as a duplicate.

however, it would be great if you could try to reproduce with an actual trunk build and feel free to reopen in case you
still should get the reported problem.

thanks


*** This issue has been marked as a duplicate of 151787 ***
Comment 5 Petr Dvorak 2009-04-28 12:07:30 UTC
Verified - duplicate (+given steps work as expected)