|[Acceleo] *.emtl files missing when building updatesite [message #774722]
||Wed, 04 January 2012 13:30
| Ingo Mohr
Registered: September 2011
I face the following problem:
When I build (or clean/rebuild) my plug-in project (with Acceleo nature and builder), the bin folder contains the *.emtl files as expected.
However, when I build the plug-in (via its feature) in an update site project, the created jar contains only *.mtl files (in addition to the Java classes) and the *.emtl files are missing.
[Updated on: Wed, 04 January 2012 13:32]
Report message to a moderator
|Re: [Acceleo] *.emtl files missing when building updatesite [message #775070 is a reply to message #775053]
||Thu, 05 January 2012 09:01
| Ed Willink
Registered: July 2009
IMHO The Acceleo 3.2 builder is unuseable because it frequently doesn't
For the MDT/OCL code generator, I therefore use Acceleo 3.1.2, and once
I am happy with the *.emtl files, I copy them from the bin tree to a
secondary Java src2 tree, remove the Acceleo nature and builder and the
customCallbacks in build.properties. This ensures that only the Java
builder is in use and it copies the *.emtl from src2 to bin, just as the
Acceleo builder might have done if it executed. This approach also
allows/requires the *.emtl to be put under configuration management,
where using the ASCII form you can check on what is changing.
On 05/01/2012 08:17, Ingo Mohr wrote:
> .. by the way: The *.emtl files are missing, too, when I export only
> the plug-in via Export->Plug-ins/Deployable Features...
Powered by FUDForum
. Page generated in 0.02377 seconds