Bug 3285 - Why does change the source attachment trigger a build (1GEHXW3)
Summary: Why does change the source attachment trigger a build (1GEHXW3)
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:52 EDT by Dirk Baeumer CLA
Modified: 2002-04-18 11:23 EDT (History)
1 user (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 Dirk Baeumer CLA 2001-10-10 22:52:35 EDT 
with autobuild on:
	- select rt.jar
	- open properties dialog
	- remove source attachment
	- press OK
	- observe: the is a build.


NOTES:
EG (5/29/01 9:03:12 PM)
	changing the source attachment changes the .classpath.
	moving to JCORE for comment. Can we diff the class path change
	and filter out changes to source attachments only?
	
PM (5/30/2001 11:20:51 AM)
	A change to the classpath file is triggering a setClasspath action which flushes the existing build state if the classpath is actually changed.
	This is a consequence of a recent change (flush build state when classpath is set). The flush could be smarter and only be performed if some non-source
	attachment info is changed.
Comment 1 DJ Houghton CLA 2001-10-23 23:53:57 EDT 
PRODUCT VERSION:
	Smoke 114
Comment 2 Jerome Lanneluc CLA 2002-04-18 11:23:12 EDT 
Verified that the builder doesn't react to changes in source attachement (build 
20020416).
Closing.