Summary: | [build path] User libraries should allow class folders | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dustin Callaway <drcallaway> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert, jerome_lanneluc, markus.kell.r, philippe_mulet |
Version: | 3.1.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Dustin Callaway
2005-11-04 11:57:57 EST
Moving to JDT UI JDT core only support class folders in the workspace. User libraries are by design only referring to external JARs so they are independent from the workspace content. Back to jdt.core. I guess external class folders are not on the plan. Build path issue. External class folders support got added in Eclipse 3.4. The support is now there are the Core level. The UI needs to be changed to allow external class folders in user libraries. >The support is now there are the Core level. The UI needs to be changed to
>allow external class folders in user libraries.
Note that you can add external class folders to the Java build path via UI - just not to a user library which is currently designed in the UI to only have archives.
Lowering prio for 3.5. Might not make it into 3.5. We won't have time to do this for 3.5. Bug 300542 implemented something similar (support for internal JARs). |