[gmf-dev] GMF MSL Adoption of EMF Transaction API

[Christian Damus <cdamus@xxxxxxxxxx>]

Hi, all,

The GMF MSL component's adoption of the EMF
Transaction API has been committed to GMF.  This will have a small
impact on MSL clients when next they adopt a GMF integration or stable
build.

Certain changes to bundle and plug-in manifests
and, possibly, code will be required in MSL clients in order to adopt GMF,
as follows:

• A new plug-in is introduced to provide transparent API compatibility for clients of the old MSL.  Existing dependencies on org.eclipse.gmf.runtime.emf.core in your bundle manifests must be changed to org.eclipse.gmf.runtime.emf.core.compatibility.  Likewise, references to the org.eclipse.gmf.runtime.emf.core.MetaModelProviders extension point ID must be changed to org.eclipse.gmf.runtime.emf.core.compatibility.MetaModelProviders.  The Java package namespaces are not changed.
• If your code was using MSL internal types from the org.eclipse.gmf.runtime.emf.core.internal.commands package (the MSLUndoStack and related types), beware that these types no longer exist.  The MSL no longer maintains an undo/redo stack.  The CommandManager/AbstractModelCommand API now is the sole implementation of an undo/redo stack in GMF.

Of course, the above changes also apply to
client code generated by GMF.

All of the public API in the org.eclipse.gmf.runtime.emf.core.compatibility
plug-in is deprecated.  The deprecation warnings should provide sufficient
information to port clients to the remaining/new org.eclipse.gmf.runtime.emf.core
API.  As soon as the rest of the GMF project has migrated off of the
compatibility plug-in, it will be deleted from the GMF repository.

Cheers,

Christian

---

Christian W. Damus
Aurora Core Model Services
IBM Rational Software
Tel: (613) 591-7937