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 224294

Summary:	AssertionError: rename folder from Send -> smthng -> send fails
Product:	platform	Reporter:	Exceptions Reporter <exceptions_reporter>
Component:	Filesystems	Assignee:	Jaroslav Havlin <jhavlin>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	P3
Version:	7.3
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	174914
Attachments:	stacktrace

Description Exceptions Reporter 2012-12-28 22:05:49 UTC

This bug was originally marked as duplicate of bug 185346, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.3 Beta 2 (Build 201211062253)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_10-b18
OS: Windows 7

User Comments:
GUEST: I try to rename folder from "Send"  to "send" with no result. Then I try to rename to some other name -- folder was renamed. But I can't rename this folder again to "send" -- this error occures.




Stacktrace: 
java.lang.AssertionError: childName: C:\Www\Crm\nbproject folderName: C:\Www\crm
   at org.netbeans.modules.masterfs.filebasedfs.children.ChildrenSupport.addChild(ChildrenSupport.java:135)
   at org.netbeans.modules.masterfs.filebasedfs.children.ChildrenSupport.rescanChildren(ChildrenSupport.java:265)
   at org.netbeans.modules.masterfs.filebasedfs.children.ChildrenSupport.getChildren(ChildrenSupport.java:89)
   at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj$FolderChildrenCache.getChildren(FolderObj.java:677)
   at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.computeChildren(FolderObj.java:173)
   at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.getChildren(FolderObj.java:155)

Comment 1 Exceptions Reporter 2012-12-28 22:05:51 UTC

Created attachment 129748 [details]
stacktrace

Comment 2 Jaroslav Havlin 2013-08-20 12:04:18 UTC

I'm sorry, I cannot reproduce the bug.
Please, can you try to reproduce it in the latest development build
and reopen the issue if the bug is still valid?
Thank you.