Community
Participate
Working Groups
I have a project which, through a classpath variable, uses an external folder as a source folder. As of 200406170800, I get the error "Required Library cannot denote external folder: ..." followed by "This project cannot be build until build path errors are resolved". This requirement that files exist in an Eclipse workspace is becoming... unreasonable. Please fix this, as it renders Eclipse completely unusable for me (and anybody else who has this type of setup).
Please explain how this setup was helping you. Basically, this wasn't supported before, and we were not flagging it. Now we do, and prevent building. You may do 2 things to bring your setup back to legal mode: - mount external directory as linked folder, then you can add it to build path - allow the Java builder to ignore and proceed on build path errors. These external folders were ignored by the JavaModel, the Java builder and causing grief to the search implementation (see bug 64646).
This is probably the wrong forum and time for me to rant against Eclipse's (ill-conceived) workspace orientation. I'll change my setup to make things "legal", and then do my screaming in 4.0. Thank you. :-)
Ok closing then.
*** Bug 69341 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Ok closing then. Well, I have also faced the same problem. I think this problem needs fixing rather than shouting back at the users. I have files to be loaded within a folder within Eclipse workspace, it will not allow adding it. It is not a project that I have control over the source code and Eclipse workspace developers cannot assume all projects that are run in Eclipse are developed using Eclipse.
See comment 1, first option. You should create a folder linked to actual location where your sources are. This could be made more transparent in the UI. Dirk: I believe you made some improvements there, didn't you ? Note: the resource limitation lies in the platform, not in JDT which is simply considering as resources whatever the platform tells it.
Yes, this got improved with 3.2 M3. There is now a "Link Source" button on the build path properties page with supports direct linking of external folders. Additionally there is a Link Source action in the Build Path context menu of the project.
