| [cross-project-issues-dev] potential breaking change effecting multiple projects |
No, no ... it's not me breaking you (this time).
I'm just a messenger. :)
We in WTP are working through some EMF changes, coming to Galileo,
and an observant extended team member (thanks John) did a scan of some code they happened to have
installed, and found a number of projects use a "forbidden field", which, the little I understand it,
means those projects will need to react to the EMF change before they can declare M5.
Is this common knowledge?
The EMF changes are described in
http://wiki.eclipse.org/EMF/EMF_2.5/Minimal_EObject_Implementation
and some potentially effected bundles are
org.eclipse.datatools.enablement.sybase.asa.models_1.0.0.v200805152355.jar
org.eclipse.datatools.enablement.sybase.ase.models_1.0.1.v200805152355.jar
org.eclipse.datatools.modelbase.sql.query_1.0.1.v200811191005.jar
org.eclipse.datatools.modelbase.sql.xml.query_1.0.0.v200807080500.jar
org.eclipse.datatools.modelbase.sql_1.0.0.v200812020844.jar
org.eclipse.tptp.platform.models.hierarchy_4.5.0.v200810100100
org.eclipse.tptp.platform.models_4.5.1.v200811200100
org.eclipse.uml2.uml_3.0.0.v200812101400.jar
So ... in the interest of sharing information and keeping our milestone smooth, thought I'd post this information,
in case it helps others.