Summary: | Build cycle treatment improvement | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Andreas Krüger <andreas.krueger> |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 2.0.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Andreas Krüger
2002-09-18 03:57:24 EDT
Your claim is fully legite. The Eclipse current build infrastructure doesn't support cycles, but this is going to change (see 2.1 plans). The responsibility lies in Platform/Core which owns the build manager, and provide a couple adjustments for this. The weak dependency approach goes in the same direction as a change we implemented in last integration build (2.1 branch). In the Java>Compiler>Other preferences, you can decide the severity of each kind of classpath problem. Cycles can be downgraded to "warning", which would let the build run smoothly. However, this still only build each project in the cycle once. Platform should still allow to further build projects in a cycle incrementally until no more change is performed (with some limit in the number of iterations, in case of misbehaving builder implementations). By doing this, only one build action (when autobuild is off) would be necessary to correctly build a cycle. Moving to Platform/Core for further comments. I think JDT/Core already does the right thing (with latest changes). Forgot to mention that the JDT/Core cycle change is also going to be backported into a 2.0.2 update. |