Summary: | Minimize recompilation | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philippe Krief <pjkrief> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | sja.eclipse |
Version: | 2.0 | ||
Target Milestone: | 2.0 F4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philippe Krief
2002-06-12 12:37:16 EDT
Please provide us with reproduceable steps. It should only recompile dependents affected by a structural change (i.e. signature change, visibility change, hierarchy change). If all you are touching is a method body, it should never cause dependent recompilation, unless you found a bug. Once thing to try too is to activate the incremental builder trace, by adding the following lines to the .options file: # Turn on debug tracing for org.eclipse.jdt.core plugin org.eclipse.jdt.core/debug=true # Reports incremental builder activity : nature of build, built state reading, indictment process org.eclipse.jdt.core/debug/builder=true then launch Eclipse with -debug mode, and make sure to use a java.exe (not a javaw.exe) VM exe, with a big console line size. It seems that since I moved to F3, the problem is not reproductible... Thanks Philippe Fair enough. Closing then. Please reopen if symptoms occur again. |