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

Bug 326975

Summary:	Eclipse Workspace Mechanic should be brought into the core platform
Product:	[Eclipse Project] Platform	Reporter:	Mike Schrag <mschrag>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	bugs.eclipse.org, fredrik.attebrant, mn, pascal, remy.suen
Version:	4.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mike Schrag

2010-10-04 17:51:38 EDT

Build Identifier: 3.6

http://code.google.com/a/eclipselabs.org/p/workspacemechanic/

This plugin set solves a very common problem that almost everyone I know has with Eclipse -- syncing properties between workspaces. This plugin works great and really should be a feature that is just available in the core runtime.

Reproducible: Didn't try

Comment 1 Markus Kuppe

2013-11-12 15:43:11 EST

Adding Robert Konigsberg as workspace mechanic project lead (as per https://code.google.com/a/eclipselabs.org/p/workspacemechanic/people/list)

Comment 2 Robert Konigsberg

2013-11-12 15:59:05 EST

Thank you. I have been aware of this bug, but am not about to work on moving this over. If there's actual interest, I'm sure I'll be contacted.

Comment 3 John Arthorne

2013-11-12 16:02:43 EST

The general answer to "Feature X should be added to core platform" is no. Unless it is a core component needed to implement the platform itself, the natural packaging is a separate feature that a user or product can install, or not, at their own discretion. It may be useful to a large number of people, but the platform is not a product that is aiming to providing everything people need out of the box. You may want to consider proposing it for inclusion in one of the major EPP packages, but first it would need to be an eclipse project I believe.

Comment 4 Markus Kuppe

2013-11-12 16:10:28 EST

See bug #421571 as follow up.