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.
Netbeans 3.2.1 Build98 on NT4 w/ Service Pack 6, PII 400 256MB of RAM. Fri Sep 28 15:18:20 EDT 2001: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:491) at java.util.ArrayList.get(ArrayList.java:307) at org.netbeans.modules.vcscore.caching.RefreshCommandSupport.getAttribute(RefreshCommandSupport.java:458) at org.netbeans.modules.vcscore.caching.RefreshCommandSupport.getStatusAnnotation(RefreshCommandSupport.java:401) at org.netbeans.modules.vcscore.VcsFileSystem.annotateName(VcsFileSystem.java:1631) at org.openide.loaders.DataNode.getDisplayName(DataNode.java:147) at org.openide.nodes.FilterNode.getDisplayName(FilterNode.java:247) at org.openide.explorer.view.VisualizerNode.<init>(VisualizerNode.java:126) at org.openide.explorer.view.VisualizerNode.getVisualizer(VisualizerNode.java:69) at org.openide.explorer.view.VisualizerChildren.added(VisualizerChildren.java:65) at org.openide.explorer.view.VisualizerEvent$Added.run(VisualizerEvent.java:83) at org.openide.explorer.view.VisualizerNode$QP.run(VisualizerNode.java:442) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154) [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:337) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
This problem is already fixed in development builds.
As I said on nbusers@netbeans.org mailing list I was not able to rep- roduce it so I verify this bug as fixed in 3.3. If you Charles encoun- ter this behavior also in development builds of NetBeans 3.3 don't he- sitate and please reopen it with further description. Thank you.
Resolved for 3.4.x or earlier, no new info since then -> closing.