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 69450 - Twice package in Explorer after rename
Summary: Twice package in Explorer after rename
Status: VERIFIED DUPLICATE of bug 69479
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-28 14:52 UTC by Milan Kubec
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (14.92 KB, image/png)
2005-11-28 14:54 UTC, Milan Kubec
Details
part of ide log (33.11 KB, application/octet-stream)
2005-11-28 14:55 UTC, Milan Kubec
Details
exception (2.08 KB, text/plain)
2005-12-01 17:05 UTC, rmatous
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2005-11-28 14:52:36 UTC
[dev-200511271900, JDK 1.5.0_05]

Package gets duplicated in Explorer Projects view after refactoring rename.

Steps to reproduce:
1) Create Java Application project
2) Create one subpackage under package called SubPackage
3) Create some classes under SubPackage
4) Invoke Refactor Rename on SubPackage package and rename it to SubPackage1
(you want to rename it to subpackage but it's not possible in one step)
5) Invoke Refactor Rename on SubPackage1 and rename it to subpackage
I ended up with two nodes with name SubPackage for the same package - see
screenshot. Both package nodes contains the same java class nodes. Source files
contain package declaration with 'subpackage'.
Comment 1 Milan Kubec 2005-11-28 14:54:04 UTC
Created attachment 27345 [details]
screenshot
Comment 2 Milan Kubec 2005-11-28 14:55:20 UTC
Created attachment 27346 [details]
part of ide log
Comment 3 Milan Kubec 2005-11-28 14:57:32 UTC
This issue is very similar to issue #61221. I've attached part of ide log when
running ide with -Dorg.openide.loaders=-5 as suggested in issue #61221.
Comment 4 rmatous 2005-11-29 18:02:34 UTC
PackageViewChildren seems to be the culprit - doesn't reflect case insensitivity
of filesystem on WINDOWS => names2nodes seems to be in inconsistent state after
capturing FileEvents. Definitely there exists two PackageViewChildren.PackageNode 
Comment 5 Tomas Zezula 2005-11-30 13:30:23 UTC
Seems as fs issue.
Comment 6 rmatous 2005-12-01 16:46:34 UTC
/cvs/openide/masterfs/src/org/netbeans/modules/masterfs/filebasedfs/fileobjects/FolderObj.java,v
 new revision: 1.16; previous revision: 1.15

/cvs/openide/masterfs/src/org/netbeans/modules/masterfs/filebasedfs/naming/NamingFactory.java,v
 new revision: 1.6; previous revision: 1.5

/cvs/openide/masterfs/test/unit/src/org/netbeans/modules/masterfs/MasterFileObjectTestHid.java,v
 new revision: 1.27; previous revision: 1.26

/cvs/openide/masterfs/test/unit/src/org/netbeans/modules/masterfs/filebasedfs/fileobjects/FolderObjTest.java,v
 new revision: 1.9; previous revision: 1.8

/cvs/openide/masterfs/test/unit/src/org/netbeans/modules/masterfs/filebasedfs/naming/FileNameTest.java,v
 new revision: 1.3; previous revision: 1.2
Comment 7 rmatous 2005-12-01 17:03:20 UTC
Windows specific bug. 

Fixed on my side. But if I repeat your steps again and again then I can almost
always make it throw any exception - related to refactoring - please evaluate. 

Comment 8 rmatous 2005-12-01 17:05:43 UTC
Created attachment 27481 [details]
exception
Comment 9 Jan Becicka 2005-12-02 07:41:26 UTC
These exceptions are harmless
Comment 10 Jan Becicka 2005-12-02 14:07:49 UTC
Checking in JMManager.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v  <-- 
JMManager.java
new revision: 1.126; previous revision: 1.125
done



*** This issue has been marked as a duplicate of 69479 ***
Comment 11 Milan Kubec 2005-12-20 10:20:54 UTC
It seems to me that this issue is not resolved correctly. It was originaly about
duplicated package nodes in Explorer view when renaimg packages and finaly after
some fixes it was duplicated to issue with some INFORMATIONAL exceptions? I
cannot reproduce the initial problem any more.
Comment 12 Milan Kubec 2006-01-16 12:28:06 UTC
Verified.
Comment 13 Quality Engineering 2007-09-20 10:56:15 UTC
Reorganization of java component