Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » EMF RCP from e3 to e4
EMF RCP from e3 to e4 [message #997234] Fri, 04 January 2013 09:52 Go to next message
Stacey Hopkins is currently offline Stacey Hopkins
Messages: 34
Registered: March 2012
Member
Happy New Year!

In the middle of doing some analysis of what's involved in migrating our emf rcp from e3 (Indigo) to e4 (Juno).... so far looks good! My runtime platform is RCP (genmodel)....but have noticed in the problems view, warnings are there for for actionSet and action (generated in the editor plugin as part of the model generation) .... which are classed as deprecated as of e4....understand there will be a backwards compatibility for the life of e4?)

....tried to do some googling on this but just seem to come across old info that seems to be out of date.

I presume this will become commands ...........or is this something silly I am doing or, is this something that is not sorted and in the pipeline to be sorted? Is there a bug for this? (again can't see anything for this???)

Thanks

[Updated on: Fri, 04 January 2013 10:22]

Report message to a moderator

Re: EMF RCP from e3 to e4 [message #997644 is a reply to message #997234] Fri, 04 January 2013 10:12 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26014
Registered: July 2009
Senior Member
Stacey,

Comments below.

On 04/01/2013 3:52 PM, Stacey Hopkins wrote:
> In the middle of doing some analysis of what's involved in migrated
> our emf rcp from e3 (Indigo) to e4 (Juno).... so far looks good! My
> runtime platform is RCP (genmodel)....but have noticed in the problems
> view, warnings are there for for actionSet and action (generated in
> the editor plugin as part of the model generation) .... which are
> classed as deprecated as of e4....understand there will be a backwards
> compatibility for the life of e4?)
Yes, as I understand it, backward compatibility will be provided for the
life of e4...
>
> ...tried to do some googling on this but just seem to come across old
> info that seems to be out of date.
>
> I presume this will become commands ...........or ss this something
> silly I am doing or, is this something that is not sorted and in the
> pipeline to be sorted? Is there a bug for this? (again can't see
> anything for this???)
There are no plans to create a alternatives to the compatibility APIs.
We'd need to rewrite (implement new versions for)
org.eclipse.emf.edit.ui/org.eclipse.emf.common.ui and everything
downstream from those would need to do the same. To maintain
compatibility we'd need to support both alternatives. The resource for
such an effort just doesn't exist!
>
> Thanks
Previous Topic:Perm Gen Error with EMF Classes on Tomcat
Next Topic:[EMF] EcoreUtil.EqualityHelper.haveEqualFeature() optimization
Goto Forum:
  


Current Time: Sat Aug 30 00:24:43 EDT 2014

Powered by FUDForum. Page generated in 0.02132 seconds