Summary: | DCR - Support for external class folders | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | assaf, bromley, bslesins, Marc.Boily |
Version: | 2.0 | ||
Target Milestone: | 2.1 | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Dani Megert
2002-01-29 04:36:20 EST
If we enable this then we should also support class path variables to refer to external folders in the UI. Moving to jdt-core for consideration. These are not on the plan for 2.0, and would be quite demanding. A reason not to consider them as external JARs is that these classfiles could change and we have no easy way to detect their changing, as opposed to JARs which content isn't assumed to change. If not, then one could simply jarify the classfiles... In order to ease the change detection process, we would need a hook onto the 'refresh from local' action, allowing us to react and check all external elements (JARs and classfiles). Then this would be acceptable maybe. Anyway, deferring post 2.0 *** Bug 8720 has been marked as a duplicate of this bug. *** *** Bug 24033 has been marked as a duplicate of this bug. *** Got addressed by using linked resource in 2.1. Closing |