Eclipse Community Forums: M2T (model-to-text transformation) » XPand template not working after upgrading to Helios

Help

Home

Home » Modeling » M2T (model-to-text transformation) » XPand template not working after upgrading to Helios

Show: Today's Messages :: Show Polls :: Message Navigator

XPand template not working after upgrading to Helios [message #542280]

Thu, 24 June 2010 12:29

chris

Messages: 72
Registered: July 2009

Member

Hi,

I have GMF editors which I generate using dynamic templates. One of my
templates (the one for the manifest file) has code like this:

«AROUND manifest FOR gmfgen::GenPlugin-»
(...)
«IF name = "ABC"-»
de.upb.somePlugin,
«ENDIF-»

However, the generated manifest does not have an import of plugin
de.upb.simePlugin.

This used to work before I upgraded to Helios, but now it doesn't any
more for some reason. I'm using GMFTools to generate my editors, and in
the involved transformation of the gmfgen model, I make sure that the
name attribute has an appropriate value (I doublechecked the generated
..gmfgen model, and its name attribute indeed contains value "ABC").

Any idea what might be going on here?

Thanks in advance,
Chris

Report message to a moderator

Re: XPand template not working after upgrading to Helios [message #542831 is a reply to message #542280]

Sat, 26 June 2010 14:47

chris

Messages: 72
Registered: July 2009

Member

> I have GMF editors which I generate using dynamic templates. One of my
> templates (the one for the manifest file) has code like this:
>
>
> «AROUND manifest FOR gmfgen::GenPlugin-»
> (...)
> «IF name = "ABC"-»
> de.upb.somePlugin,
> «ENDIF-»
>
>
> However, the generated manifest does not have an import of plugin
> de.upb.simePlugin.
>
> This used to work before I upgraded to Helios, but now it doesn't any
> more for some reason. I'm using GMFTools to generate my editors, and in
> the involved transformation of the gmfgen model, I make sure that the
> name attribute has an appropriate value (I doublechecked the generated
> .gmfgen model, and its name attribute indeed contains value "ABC").

In case somebody runs into the same problem: replace " by '.

Cheers,
Chris

Report message to a moderator

Re: XPand template not working after upgrading to Helios [message #542988 is a reply to message #542831]

Mon, 28 June 2010 06:39

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

This is related to GMF's modified version of Xpand, right?

Sven

chris schrieb:
>> I have GMF editors which I generate using dynamic templates. One of my
>> templates (the one for the manifest file) has code like this:
>>
>>
>> «AROUND manifest FOR gmfgen::GenPlugin-»
>> (...)
>> «IF name = "ABC"-»
>> de.upb.somePlugin,
>> «ENDIF-»
>>
>>
>> However, the generated manifest does not have an import of plugin
>> de.upb.simePlugin.
>>
>> This used to work before I upgraded to Helios, but now it doesn't any
>> more for some reason. I'm using GMFTools to generate my editors, and in
>> the involved transformation of the gmfgen model, I make sure that the
>> name attribute has an appropriate value (I doublechecked the generated
>> .gmfgen model, and its name attribute indeed contains value "ABC").
>
> In case somebody runs into the same problem: replace " by '.
>
> Cheers,
> Chris

--
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: XPand template not working after upgrading to Helios [message #629455 is a reply to message #542280]

Tue, 28 September 2010 11:06

Laura Hernández

Messages: 22
Registered: September 2009

Junior Member

Hi Chris,

did you solve your problem changing " by ' ?

I have the same problem, I get an error trying to generate the code with dynamic templates after upgrading to Helios version, but I don't use double quote in these templates.

This is the error I got:
Exception (org.eclipse.gmf.internal.xpand.util.ParserException, @aspects::impl::diagram::editparts::NodeEditPart
[unspecified location] (5) ; ">") while generating code

Any clue? Maybe a ">" symbol not recognized? this template was correct with the previous version.

Thanks!!

Laura.

Report message to a moderator

Previous Topic:	Iterating over extensions
Next Topic:	[Acceleo] Debugging problems with propertys

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jan 19 04:42:42 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter