Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [MWE] JavaMetaModel change from 0.7 to 0.8
[MWE] JavaMetaModel change from 0.7 to 0.8 [message #520065] Thu, 11 March 2010 02:17 Go to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi,
I am not sure if this is a MWE or Xtend question. I noticed that in Helios I needed to use another JavaMetaModel class
in my workflow definition (org.eclipse.xtend.type.impl.java.JavaMetaModel) than in Eclipse 3.5 version 0.7
(org.eclipse.internal.xtend.type.impl.java.JavaMetaModel).

Is there a way to specify the JavaMetaModel in a workflow which remains valid going from Eclipse 3.5 to Eclipse 3.6?

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org

Report message to a moderator

Re: [MWE] JavaMetaModel change from 0.7 to 0.8 [message #520993 is a reply to message #520065] Tue, 16 March 2010 05:41 Go to previous message
Sven Efftinge is currently offline Sven EfftingeFriend
Messages: 1823
Registered: July 2009
Senior Member
No, we have just renamed the class (internal didn't make sense).
You could of course create a class
org.eclipse.internal.xtend.type.impl.java.JavaMetaModel) which extends
org.eclipse.xtend.type.impl.java.JavaMetaModel to add backward
compatibility.
We didn't do so, because a lot of stuff was missplaced in 'internal'
packages.

Sven

Martin Taal schrieb:
> Hi,
> I am not sure if this is a MWE or Xtend question. I noticed that in
> Helios I needed to use another JavaMetaModel class in my workflow
> definition (org.eclipse.xtend.type.impl.java.JavaMetaModel) than in
> Eclipse 3.5 version 0.7
> (org.eclipse.internal.xtend.type.impl.java.JavaMetaModel).
>
> Is there a way to specify the JavaMetaModel in a workflow which remains
> valid going from Eclipse 3.5 to Eclipse 3.6?
>


--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Re: [MWE] JavaMetaModel change from 0.7 to 0.8 [message #622323 is a reply to message #520065] Tue, 16 March 2010 05:41 Go to previous message
Sven Efftinge is currently offline Sven EfftingeFriend
Messages: 1823
Registered: July 2009
Senior Member
No, we have just renamed the class (internal didn't make sense).
You could of course create a class
org.eclipse.internal.xtend.type.impl.java.JavaMetaModel) which extends
org.eclipse.xtend.type.impl.java.JavaMetaModel to add backward
compatibility.
We didn't do so, because a lot of stuff was missplaced in 'internal'
packages.

Sven

Martin Taal schrieb:
> Hi,
> I am not sure if this is a MWE or Xtend question. I noticed that in
> Helios I needed to use another JavaMetaModel class in my workflow
> definition (org.eclipse.xtend.type.impl.java.JavaMetaModel) than in
> Eclipse 3.5 version 0.7
> (org.eclipse.internal.xtend.type.impl.java.JavaMetaModel).
>
> Is there a way to specify the JavaMetaModel in a workflow which remains
> valid going from Eclipse 3.5 to Eclipse 3.6?
>


--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Previous Topic:[MWE] getting to the issues in the WorkflowRunner
Next Topic:[MWE] getting to the issues in the WorkflowRunner
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Apr 26 11:36:13 GMT 2024

Powered by FUDForum. Page generated in 0.03691 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly