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

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 https://bugs.eclipse.org/bugs/show_bug.cgi?id=332474 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=332490 for more information.

Cheers,

Kenn

On Wed, Dec 15, 2010 at 3:36 PM, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
Hm...
 
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)?
 
 
Thanks,
--
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
Sent: Mittwoch, 15. Dezember 2010 21:12
To: Eclipse Cross Project Issues
Subject: [cross-project-issues-dev] EMF Contribution to Indigo M4

Team,

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 https://bugs.eclipse.org/bugs/show_bug.cgi?id=332614 for details.

Cheers,

Kenn


_______________________________________________
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