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

Bug 48637

Summary:	Need mechanism for migrating nature ids and builders in .project
Product:	[Eclipse Project] Platform	Reporter:	Ritchie Schacher <schacher>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	danberg, mdelder, pombredanne
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Ritchie Schacher

2003-12-12 09:28:20 EST

If you rename a plugin, or move a nature or builder from a plugin, then old 
projects in an old workspace will be invalid.

We had discussed the idea of adding an extension point that maps an old 
nature/builder id to a new nature/builder id.  Then the platform can detect 
the .project needs migration and put a quick fix in the task list.

Comment 1 Michael D. Elder

2004-01-28 16:23:25 EST

We have built an extendible Tacit Migration Engine which solves this problem for
us. Clients can implement one of two extension points
(org.eclipse.wtp.migration.natureMapping,
org.eclipse.wtp.migration.builderMapping). The extension points define a list of
old values and the new value. The engine will migrate those existing values to
the new values automatically. The system does not require any action on the part
of the user, and does not require that the Plugin Developer implement any code.

Comment 2 John Arthorne

2006-06-12 14:28:59 EDT

Extensions can now be contributed to other namespaces, so it is possible to move a builder/nature to another plugin and still have the same fully qualified builer/nature id.  This makes the need for a migration facility less compelling.