|[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
and some potentially effected bundles are
So ... in the interest of sharing information and keeping our milestone smooth, thought I'd post this information,
in case it helps others.
Back to the top