The 4.2 builds are consuming a "base" EMF, which are the base parts of EMF that don't depend on the rest of Eclipse. The EMF team were kind enough to split their build into two pieces so that it could be consumed by the platform.
The 4.2M2 build contains the EMF M2 base from the p2 repository http://download.eclipse.org/modeling/emf/emf/2.8milestones. Please note that the remainder of the EMF M2 SDK does not yet exist. There is a circular dependency between EMF and the platform as a whole, which is handled by splitting EMF into two. It is better for the 4.2 milestone to target the version of EMF that will be EMF M2 instead of an IBuild that has been published but will be out of date once M2 is declared. The problem is just for a short time while the remainder of the EMF M2 contribution needs to be completed. Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=356644, where the 4.2 SDK will be restructuring its dependencies to tolerate having a range of EMF versions installed. I raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=358220 about updating the 4.2 download page with appropriate links once those are available from EMF. -Andrew From: "Konstantin Komissarchik" <[email protected]> To: "'E4 Project developer mailing list'" <[email protected]> Date: 09/19/2011 09:33 PM Subject: Re: [e4-dev] Can we add EMF-I-Build to predefined updatesites Sent by: [email protected] Where is E4 consuming EMF builds from anyway? We are currently blocked from adopting 4.2 M2 because I cannot find the matching EMF I-Build. The latest I-Build published on EMF downloads page is from 9/13, while 4.2 M2 includes EMF bundles stamped with 9/16. Stuff like this is pretty frustrating for adopters who are trying join the big 4.2 is primary for Juno push. Here are some concrete suggestions for making life easier for adopters: 1. Eclipse 4.2 download page should include link/reference to the exact EMF build that was used. 2. Eclipse 4.2 should refrain from adopting EMF builds before they are published on EMF download page. Note that pointing adopters at the EMF’s I-builds repository does not work as not every adopter can consume in this manner. In our case, we need a zipped repo that is only available for published EMF builds on the downloads page. Thanks, - Konstantin_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
