Community
Participate
Working Groups
When i want to add a folder variable to my build-path for my project (c:/eclipse/workspace) i get the following error which disallows me from rebuilding my project : "Required library cannot denote external folder: 'C:\eclipse\workspace' for project interpharm" This error has only appeared in the final 3 release on eclipse ???
Steps to reproduce: 1) Create a Java project at the default location 2) Open build path properties page 3) On "Libraries" page, click "Add Variable" 4) Click "Configure Variables" 5) Create a new variable called TEMP at C:\temp (ensure this directory exists) 6) Add this variable to the libraries list for the project -> The project cannot be built. Error: Required library cannot denote external folder: 'C:\temp' for project J1
We documented this issue in the readme (eclipse\readme\readme_eclipse.html). Classpath entry denoting external class folder is now properly rejected ----------------------------------------------------------------------- Although external class folders (i.e., folder containing .class files and located outside workspace) were never properly supported by the JDT, a problem was never reported when constructing such a build path. JDT now properly diagnoses a problem in this situation. In order to still benefit from external .class files, a class folder must be mounted as a linked folder in Eclipse workspace (in project properties, select Java Build Path > Libraries > Add Class Folder > Create New Folder... > Advanced. Then a folder name can be associated with an arbitrary file system location by checking "Link to folder on the file system). Once mounted, the linked class folder can normally be referenced on a build path, and from there on programs can be compiled against it. (bug 67631) *** This bug has been marked as a duplicate of 67631 ***
The solution you describe there doesn't seem to apply to our situation. I think one should have the possibility to reference a folder through a variable to offer the possiblity to change the folder at once for all projects. Going through a variable also allows different users to have the target directory in different places. In our case, we have different test (JUnit) projects where all of these projects point to a variable (common) pointing to a local folder (particular to user) which contains properties files used for the testing. Using the method you describe above will introduce a local folder in the project classpath which is not wished. Could you please tell me what is your suggested solution for this? Or is it the one suggested in bug 70417?
