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.
Summary: | IndexOutOfBoundsException when files deleted outside netbeans | ||
---|---|---|---|
Product: | obsolete | Reporter: | support <support> |
Component: | vcscore | Assignee: | issues@obsolete <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | ppisl |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Other | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Exceptions thrown while canceling RMI object. |
Description
support
2001-08-03 12:33:14 UTC
*** Issue 13620 has been marked as a duplicate of this issue. *** This problem was already reported by someone (but I can not find an issue for it). It's already fixed in development builds. BTW: you are right, that the bug is actually in vcscore. I have to unfortunately reopen the bug because it still occurs in the latest development build #200108080100 of NetBeans 3.3 and reproducti- on in Forte for Java 3.0 FCS is quite easy. 1. Mount CVS filesystem using Command-line Client. 2. Create new RMI_Object using "New|RMI|UnicastRemoteServer (group)" in the root of your CVS filesystem. 3. Close the editor and "Compile" "RMI_ObjectImpl [Local]" node. 4. Do "CVS|Refresh" on the root of your CVS filesystem. 5. Invoke "Tools|Cancel RMI" on "RMI_ObjectImpl [Local]" node. 6. Exception should appear after a while. 7. If you are not successful with reproduction delete all RMI_Object* files externally, wait until they disappear from FS and repeat it. For more details have a look at the exceptions attached. Created attachment 2101 [details]
Exceptions thrown while canceling RMI object.
Well, it should be fixed in dev builds. I can not reproduce it any more. I did various hanky-panky but was not able to reproduce the exception so I guess it got fixed. Verified in development build of NetBeans 3.3 #200110230735. Addind Petr on CC, since users complain about this on nbusers@netbeans.org. [FFJ CUSTBUG] This bug should be included in the next jumbo patch since at least 3 external users have encountered it. Exception is never thrown again but if RMI object is canceled all class fileobjects don't work together with VCS filesystem. Due to missing sta- tus information it seems like annotateName() is not called. Popup menu is shown but no action can be invoked and those class files can't be version controlled anyhow. Could somebody from Sustaining team investigate it ? No comments from sustaining guys...seems like whisper fix:-/ Well, No E. is thrown, but problems with unaccessible CVS actions/commands still persist (tested with JP) Resolved for 3.4.x or earlier, no new info since then -> closing. |