Community
Participate
Working Groups
I20030206 - create a Java project - select new Folder - enter name link Link the folder to an existing workspace. Observe: the package explorer shows a lot of resource having the ghost icon and named link..metadata..config.* PLEASE NOTE: don't delete the link folder since this will delete the content of the link as well, also state otherwise
The strange rendering is caused by folders and files starting with a .
I think the Java Model treats these folders as packages but gets confused by the . in the name.
Here is a first analysis for the follwing small test case: - create normal projetc Test - create a folder link under c:\tmp - create a folder .folder in link - create a file in folder .folder - create a folder link under Test. Use the advance settings and link it to c:\tmp\link The Java Model treats the new folder link and its sub folders as packages, resulting in a package link..folder which seems to confuse the Java Model. When we receive the IPackageFragement for rendering exists() on the package returns false; I would expect that link..folder isn't reported as a package fragment. Moving to JDT/Core for comments
Jerome - aren't we eliminating .names from valid Java package segment name ?
Note this is not a problem with link folder. If you create a folder p and a subfolder .folder under the project in the file system and do a refresh, you see the same behavior. Problem is with the DeltaProcessor that adds subpackages without verifying it is a valid package name. Fixed and added regression test JavaElementDeltaTests.testAddInvalidSubfolder()
Verified.
