Bug 218614 - [implementation] Should not build if expanded classpath has not changed
Summary: [implementation] Should not build if expanded classpath has not changed
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: performance
Depends on:
Blocks:
 
Reported: 2008-02-12 07:08 EST by Jerome Lanneluc CLA
Modified: 2019-11-29 09:40 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2008-02-12 07:08:32 EST 
I20080207-1530

If the classpath of several projects are changed so that the expanded classpath of  a dependent project is not changed, then we should optimize this case and not force the dependent project to be built.
Comment 1 Olivier Thomann CLA 2011-03-15 11:36:21 EDT 
Jay, please check if this is still an issue.
Comment 2 Eclipse Genie CLA 2019-11-29 09:40:13 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.