Bug 61758 - Building workspace does too much work
Summary: Building workspace does too much work
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-11 12:56 EDT by Jeremy Wohl CLA
Modified: 2004-05-19 12:35 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Wohl CLA 2004-05-11 12:56:27 EDT
With build-on-resource-mod turned on, releases 3M7 and 3M8 do far more work than
their predecessors.

Where making a single, non-cascading change to a Java source file in release
3M6, let's say, caused a brief (<2 seconds) incremental build, and non-Java
files caused essentially no pause -- newer releases have unpredictable results.
 Often, a single change causes 20 seconds of building (and a fairly locked up
environment) when the change is Java-related or not.

I've tried "priming" new Eclipse runs with full clean builds, hoping all future
mods would cause mild interruptions, but it doesn't seem to matter.

For reference, I'm running a 2Ghz P4 with lots of free RAM and Eclipse memory
-Xmx256m.
Comment 1 Jeremy Wohl CLA 2004-05-11 16:17:42 EDT
Looking at the progress view shows a compile spin through all packages. 
Sometimes I even see a "cleaning output folder" or somesuch.  Again, incremental
(very brief) builds do occur, but mixed in will long-winded cycles.  All trivial
source changes.
Comment 2 Jeremy Wohl CLA 2004-05-11 18:26:06 EDT
Nevermind, someone sneaked an oft-changing library into the project.  !!!