Eclipse Community Forums: M2T (model-to-text transformation)

Home » Modeling » M2T (model-to-text transformation) » [Acceleo] PDE and EMTL(EMTL files are not generated during pde build)

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

[Acceleo] PDE and EMTL [message #689649]

Tue, 28 June 2011 05:07

Brice Pajot

Messages: 4
Registered: June 2011

Junior Member

Hi,

Using Eclipse Indigo (3.7.0) with Acceleo 3.1.0, I got a problem while trying to export my Acceleo plugins. The produced plugins do not contain the expected EMTL files, which generates errors at runtime.The behavior is the same using either the "export deployable plugins" Eclipse command or the headless build.
Just note that the behavior in 3.6.0 was not the same (not sure for 3.6.1 and 3.6.2). I also succeeded in reproducing the same behavior by using a fresh install of the Eclipse product with a fresh new acceleo project using a public available URI (Ecore).

Looking at what is generated through PDE build ant task, it seems that an EMTL file is actually generated just besides the build directory (@dot) as a "@dot.emtl" file, which may explain why it is not finally present in the generated plugin.

By having a quick look at the AcceleoCompiler Task code (computeFileInfos method in AcceleoCompilerHelper), it seems that the previous (normal?) behavior can be obtained by setting an output folder equals to the source folder (outputFolder="${target.folder}") in the task defined in the "build.acceleo" file. However, I am not sure this is one of the best practices.

So, my question(s): what is the "normal" behavior expected with Acceleo 3.1.0 regarding the plugin export? did I do something wrong?

Report message to a moderator

Re: [Acceleo] PDE and EMTL [message #689901 is a reply to message #689649]

Tue, 28 June 2011 15:05

Stephane Begaudeau

Messages: 458
Registered: April 2010
Location: Nantes (France)

Senior Member

Hi Brice,

It seems that a regression has appeared in the generation of the build.properties file.
Quote:

it seems that the previous (normal?) behavior can be obtained by setting an output folder equals to the source folder (outputFolder="${target.folder}") in the task defined in the "build.acceleo" file. However, I am not sure this is one of the best practices.

Even without the "outputFolder="${target.folder}" it should work but I've looked at the code and a regression has appear. You can indeed restore the previous behavior by adding "outputFolder="${target.folder}". Thanks for reporting this issue, I've fixed it. The fix will be available when Acceleo 3.1.1 will be released.

Regards,

Stephane Begaudeau, Obeo

--
Twitter: @sbegaudeau
Blog: http://stephanebegaudeau.tumblr.com
Acceleo Documentation: http://docs.obeonetwork.com/acceleo

Report message to a moderator

Re: [Acceleo] PDE and EMTL [message #689914 is a reply to message #689901]

Tue, 28 June 2011 15:24

Brice Pajot

Messages: 4
Registered: June 2011

Junior Member

Hi Stephane,

Thanks for these clarifications.

Regards,

Brice.

Report message to a moderator

Re: [Acceleo] PDE and EMTL [message #1701407 is a reply to message #689649]

Mon, 13 July 2015 09:18

Fabian Meyer

Messages: 7
Registered: September 2013

Junior Member

I'm having the same error right now, using Luna Service Release 2 (4.4.2). The exported plug-ins do not contain the .emtl files. The binary folder of the eclipse project contains the .emtl files, but they are not exported.

Report message to a moderator

Previous Topic:	[Acceleo] Out of memory
Next Topic:	Android Code Generation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 26 21:59:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter