Re: [e4-dev] [releng] 4.1 M6

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Thanks Paul - using EMF from their update-site (btw the one
preconfigured is not the correct one) things installed like a charme!

Thanks

Tom

Am 13.03.11 18:51, schrieb Paul Webster:
> On Sun, Mar 13, 2011 at 1:23 PM, Tom Schindl
> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     This is just a wild guess but I think the problem is the feature
>     definition because emf.common is part of the plugin list in the feature
>     and not a dependency. Is this correct?
> 
> 
> The 4.1 build is picking up the EMF ecore/common M6 that Ed mentioned. 
> They promote those 2 as +0 components.  We pick them up from
> http://download.eclipse.org/modeling/emf/emf/updates/2.7milestones/base/
> 
> 
> But Indigo still has the M5 features in it.  I was able to install the
> M5 EMF SDK org.eclipse.emf.sdk_2.7.0.v20110128-1446 into my 4.1 install
> that contained the EMF M6 core features:
> org.eclipse.emf.common_2.7.0.v20110310-1642 and
> org.eclipse.emf.ecore_2.7.0.v20110310-1642 and it didn't complain, so
> I'm not sure what's up with that :-)
> 
> If this is really just the mismatch between the +0 components and
> /releases/indigo (which still has M5 in it) then you might be able to
> prove it by installing EMF ecore and common from the 2.7 milestone repo
> first.  Once Indigo moves up to M6 it will clear itself up.
> 
> PW
> 
> 
> -- 
> Paul Webster
> Hi floor.  Make me a sammich! - GIR
> 
> 
> 
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev