Summary: | [M1] dependency checking too conservative | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Ilja Preuss <preuss> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Ilja Preuss
2002-09-30 03:47:38 EDT
Kent - can you please double check what would be going on ? Would refactoring touch all these source files for no particular reason ? Tried to reproduce but didn't see anything abnormal. Only the one file was being recompiled. Ilja: can you reproduce with the builder trace enabled? Start eclipse with a command line like: d:\R2.0\eclipse\eclipse.exe -debug -consolelog -data d:\R2.0\workspace\plugins - vm d:\jdk1.3\bin\java.exe -vmargs -Xmx150mb Make sure to run java.exe not javaw.exe with -debug -consolelog after creating a .options file in the same directory as eclipse.exe with: # Turn on debug tracing for org.eclipse.jdt.core plugin org.eclipse.jdt.core/debug=true # Reports incremental builder activity org.eclipse.jdt.core/debug/builder=true Ilja: can you reproduce with the builder trace enabled? We need more information... I currently don't have the time, sorry (it's a little bit complicated because we have a network installation of eclipse). Possibly I will find the time at the end of the week. Tried to reproduce but could not. Reopen if you find repeatable steps. |