Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] EMF Contribution to Indigo M4

At this point, the 4.1SDK is using the original EMF M4.  If you were to look in the Install New Software dialog, with the repository
then you see newer versions of some of the core emf.  These newer versions are the M3 content, and now I guess also the M4a content.  They won't be installable since they will conflict with the dependency from the e4 product to emf.


From: Kenn Hussey <kenn.hussey@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 12/15/2010 04:04 PM
Subject: Re: [cross-project-issues-dev] EMF Contribution to Indigo M4
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

Well, inclusion of the build ID in the p2 metadata actually affects how versions are generated by Buckminster. As a side effect, some of the EMF features/bundles ended up with "older" versions in the M4 build (compared to M3), resulting in an inconsistent repository. See and for more information.



On Wed, Dec 15, 2010 at 3:36 PM, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
how had EMF been affected by this? If it's just a missing build ID in about.mappings, is this really worth a respin?
Also, does this affect e4 (Eclipse SDK 4.1 m4)?
It does seem related to ...
Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Kenn Hussey
Mittwoch, 15. Dezember 2010 21:12
Eclipse Cross Project Issues
[cross-project-issues-dev] EMF Contribution to Indigo M4


Just a heads up that we have had to publish and contribute an M4a build of EMF (base and core) due to a versioning problem in Buckminster that was caused by a change in p2. Please see for details.



cross-project-issues-dev mailing list


cross-project-issues-dev mailing list

Back to the top