Bug 246637 - Build Path->Use as Source Folder doesn't work across linked folders
Summary: Build Path->Use as Source Folder doesn't work across linked folders
Status: VERIFIED DUPLICATE of bug 243692
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.5 M2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-08 15:42 EDT by Brian Anderson CLA
Modified: 2008-09-16 05:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Anderson CLA 2008-09-08 15:42:48 EDT
Build ID: I20080617-2000

Steps To Reproduce:
1. Create a project and add a regular directory that is linked to a file system folder.  My linked folder is the root of my source tree which has over 200 sub-directories each of which contains code for a jar file and so has its own "src" directory.
2. Open the linked folder and navigate to a nested sub-directory:  in my case something like "coreServices/src".
3. Right-click->Build Path->Use as Source Folder

When I initially create the project this works: the directory I selected disappears and appears as a source folder in the project.  However after a while (even if I've never closed the project and exited eclipse) this gesture will stop working:  the directory may or may not disappear from the linked folder, but it will not appear as a source folder in the project.

If it happens to still show the directory in the linked folder and I repeat the gesture,  I will get an error dialog about the folder already is a source folder.

If I go to the project properties and look at the Java Build Path, Source tab,  I do not see the source directory.  I can add the directory from this tab however and then it will appear as a source folder in the project


More information:
There is nothing in the log.
Comment 1 Brian Anderson CLA 2008-09-10 17:55:11 EDT
It turns out that I have one non SDK plugin:  perforce.  If I remove this I can add the source directory fine.
Comment 2 Jerome Lanneluc CLA 2008-09-12 06:45:58 EDT

*** This bug has been marked as a duplicate of bug 243692 ***
Comment 3 David Audel CLA 2008-09-16 05:38:18 EDT
Verified for 3.5M2