Maven Environment for Turbine Applications (M.E.T.A.)

The Maven Environment for Turbine Application (M.E.T.A.) helps you to write applications based on the Turbine Web application framework.

How it works

M.E.T.A. builds an application skeleton from a set of pre-built configuration files and some user supplied parameters. Most of the parameters have reasonable defaults, only the application name must be given at setup time.

Parameters are supplied either on the command line (if you want to rapid prototype an application, you can do so by running a single command) or with a special properties file, which is read by M.E.T.A. when you setup your appliation. Please see the Getting Started page for a reference on how to bootstrap your application.

Maven Integration

M.E.T.A. is installed as a maven plugin and has goals and properties.


All M.E.T.A. goals are prefixed by "turbine" in the maven environment. While "meta" is distinctive in the Turbine context, using meta:<xxx> as goal names proved confusing in the Maven context (is meta:<xxx> a maven meta-goal or is it part of the M.E.T.A. environment?). So the M.E.T.A. environment uses the "turbine:" prefix.

The available goals are listed on the Goals page.


To adjust the various parameters of the plugin to your application, you must set properties in your or file. Most of the properties have a reasonable default. You can find the complete list of properties on the Properties page. If you use the turbine:setup goal from M.E.T.A., these properties are preset either from the command line parameters or from the parameters set in the setup properties file.

As M.E.T.A. tries to integrate with the maven web application environment as seamlessly as possible, it requires a few properties from other plugins to be set.