Bug 93135 - Build path libraries should be allowed to be of type external folder
Summary: Build path libraries should be allowed to be of type external folder
Status: RESOLVED DUPLICATE of bug 77113
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 11:49 EDT by Sébastien Gandon CLA
Modified: 2007-06-19 09:36 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sébastien Gandon CLA 2005-04-28 11:49:52 EDT 
Hi there,

I am very surprised to see this limitation in Eclipse as to not allow creation
of  a library entre pointing to an external (to the workspace) folder.
To me a Jar file is just a virtual folder so I do not see why external jars are
allowed and not external folders?

Please make this limitation go away as it seem to anoy and surprise many people.

SeB.
Comment 1 Brian Thomson CLA 2005-07-12 08:24:53 EDT 
This affects PDE.
I develop against a Target some of whose plugins contain folders as well as
jars.  When PDE computes the build path for me, it naturally includes those
folders, which prompts the "Required library cannot denote external folder" error.
It tells me to fix the build path but of course I can't, because I can't
manually edit the entries under the "Plug-in Dependencies" library.
Comment 2 Frederic Fusier CLA 2007-06-19 09:36:24 EDT 

*** This bug has been marked as a duplicate of bug 77113 ***