Martin Taal's Blog

About EMF, Teneo, CDO, Texo, Hibernate, Open-Source ERP and other topics

EMFT Texo: integrating Texo in your build process

with one comment


The latest Texo version supports headless/server code generation directly from Java or ANT. This makes it possible to integrate Texo code generation in your overall build process.

So how to setup headless/build-integrated code generation?

Texo uses Eclipse for code formatting and import resolving. So, start by downloading an Eclipse version suitable for your build platform. Then install the Texo plugins in this Eclipse version through the Texo update site and put this Eclipse version somewhere on your build server.

As a second step choose a location on the build server where Texo can create a workspace and Java project. And last, place the model (ecore/xsd) files on the build server.

To generate code using ANT you can use a macrodefinition. To run the macro:

<texo.gen eclipse=”/home/build/eclipse”




jpa=”true” dao=”false”/>

The parameters have the following meaning:

  • eclipse: the eclipse installation location
  • data: the workspace location
  • projectName: the name of a Java project to use, see here for more information
  • modelLocation: the location of the model files
  • jpa: generate code with JPA annotations
  • dao: generate a DAO layer

The generated code will be present in the Java project on your build server and can be copied/compiled from there.

Instead of using ANT, you can also execute headless code generation directly in Java.

That’s all, with these latest developments, code generation and your build process can be nicely tied together!

Thanks for reading and I hope this blog post helps to give Texo a try. Visit the Texo wiki for more information. Let me know if you have any questions or remarks on the EMFT newsgroup or forum!

gr. Martin

Written by martintaal

October 21, 2012 at 9:25 pm

Posted in Texo

One Response

Subscribe to comments with RSS.

  1. I was testing TEXO today i am very happy, i can generate clases according to JPA specification and what is better i can modify the generated code using “@NOT generated”
    if i have a large model then i can split it in several ecore file and generate code.
    thanks a lot!


    April 28, 2014 at 2:38 am

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: