Bugzilla – Full Text Bug Listing
| Summary: | Cannot nest entries in Java Build Path - Request for Feature Removal | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Michael Erdmann <michael_erdmann> |
| Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chase |
| Version: | 2.0.1 | ||
| Target Milestone: | 2.1 M4 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
We are planning on allowing to nest source/lib folders as long as exclusion patterns are specified. This is on the plan for 2.1-M4. *** Bug 26806 has been marked as a duplicate of this bug. *** Changed JavaConventions to allow this scenario. Verified. |
In Projet/Preferences/Java Build Path/Libraries after pressing Advanced I would like to add an existing folder to the classpath. This works fine as long as I do not try to add a sub- or super-folder of an existing one. As I understand this is intended behavior. But in some scenarios it makes sense, e.g. to point to a properties file in the root directory, whereas some other jars, libs are in subdirectories. Thus, my de-enhancement request. thanks, michael