Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] potential breaking change effecting multiple projects


Hi All,

I noticed that the UML2 plugin appeard in the list mentioned below and I just wanted to reassure everyone that  the latest build of UML2 has all the necessary changes to accomodate the EMF change.
The latest UML2 build is:  I200901211303.

By the way, not only did I need to regenerate my API but I also needed to make minor changes to accomodate new exceptions that were being thrown.   Even if you get your component compiling, some light sanity checking of your component might be a good idea after adopting the EMF change ;)

Cheers,
- James.



brian.fitzpatrick@xxxxxxxxxx
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

22/01/2009 05:14 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
Re: [cross-project-issues-dev] potential breaking change        effecting        multiple projects






Thanks for letting us know. We'll look into the impact for M5.


Brian Fitzpatrick
Eclipse Data Tools Platform PMC Chair
Eclipse Data Tools Platform Connectivity Team Lead
Staff Software Engineer, Sybase, Inc.



David M Williams <david_williams@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

01/22/2009 02:20 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
cross-project-issues-dev@xxxxxxxxxxx
cc
Subject
[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.

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top