Summary: | [quick fix] New Quick Fix: Refresh "missing" libraries and paths | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Andrew Hayden <andrew.hayden> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P4 | ||
Version: | 3.1.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Andrew Hayden
2005-11-01 16:08:28 EST
Assuming we had a 'refresh JAR' quick fix, I think it would be too late as the build state is already gone and a rebuild can't be avoided. Philippe, is that correct? Hm, I should probably clarify this request some more. A major part of the inconvenience that is caused is the refresh of literally tens of thousands of files in the project just so that Eclipse will re-scan the directories and library entries that specifically have disappeared. I could probably go pick each individual one out by hand, but that would also be a large waste of time. Maybe an "easy" solution would be to simply make the quick fix to be a "attempt to refresh all missing library/sourcepath/classpath entries" that would selectively refresh all those things in the project that seem to be missing, without refreshing the other 99% of the world. |