Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 116473

Summary:	[Subscribers] Synchronizing kicks off many builds
Product:	[Eclipse Project] Platform	Reporter:	Jared Burns <jared_burns>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	ryanman
Version:	3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:	stalebug

Description Jared Burns

2005-11-15 13:27:18 EST

Build 3.2 M3
Observed on Linux-GTK and WinXP

1. Start a workspace synchronization from the Synch view.
2. Open the Progress view to watch the synch job.
3. For the entire duration of the synchronization job, a job named "Building
Workspace" is created and quickly goes away many times.

This build job doesn't appear to be doing much, but it's still a waste of
resources for it to be coming and going so often. Synchronizing the workspace
should be a read-only operation, so I don't understand why it's kicking off so
many builds.

Comment 1 Michael Valenta

2005-12-06 15:28:48 EST

This is a side effect of us using the Core ISychronizer to persist our remote state. It would be nice if we could break the dependency so we could be freed from the workspace but it is too much work to consider for 3.2.

Comment 2 Eclipse Webmaster

2019-09-06 16:13:20 EDT

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.

Comment 3 Eclipse Genie

2022-02-12 13:34:58 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.