Community
Participate
Working Groups
This enhancement addresses the following requirements: 1) Analysis of what needs to be deprecated in the GMF MSL API and implementing the @deprecated tags with appropriate documentation. 2)Re-implementation of the deprecated APIs as delegation to/extension of the EMF-TX and workbench APIs. Goal is to pass all existing JUnits.
Created attachment 34343 [details] Refactoring of emf.core/emf.core.compatibility plug-ins The attached patch refactors the org.eclipse.gmf.runtime.emf.core plug-in into two plug-ins: the original and a new org.eclipse.gmf.runtime.emf.core.compatibility. The latter plug-in defines the deprecated APIs that the Common, Diagram, and CodeGen components will need to migrate from to the new TransactionalEditingDomain-based API in org.eclipse.gmf.runtime.emf.core. To that end, the warnings should indicate the replacements for the deprecated APIs. In the mean-time, to use the compatibility plug-in, it is necessary to make the following changes in all clients of the org.eclipse.gmf.runtime.emf.core plug-in: - replace the org.eclipse.gmf.runtime.emf.core dependency in your bundle manifest with org.eclipse.gmf.runtime.emf.core.compatibility - replace references to the org.eclipse.gmf.runtime.emf.core.MetaModelProviders extension point ID with org.eclipse.gmf.runtime.emf.core.compatibility.MetaModelProviders
Patch committed by Linda.
Added dan to the cc list
[target cleanup] 1.0 M5 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Runtime EMF was the original product and component for this bug