M.E.T.A. uses two sets of plugin properties to configure your Turbine application. The first set is called the "Setup Properties", because they're only read by the turbine:setup goal which is run when creating the skeleton of your application. These parameters are used in various places and transformed into your turbine specific configuration files. Once you've set up your application, these parameter are no longer used. If you change these, you must rerun the turbine:setup goal (which might result in losing other changes to your configuration files, so be careful!).
| Property | Optional? | Default value | Description |
|---|---|---|---|
| turbine.app.name | No | no default value | Name of the new application. Must be set for turbine:setup, else the goal fails! |
| turbine.app.flavor | Yes | turbine-2.3.2 | Defines the dependencies and the release version of Turbine that the new application should use. Currently supported versions are:
|
| turbine.app.om.layer | Yes | torque | Defines the OM layer which is configured and used with Turbine to access database information. Currently supported settings are:
|
| turbine.app.subdir | Yes | true |
|
| turbine.app.setup.demo | Yes | true | If true, copy the demo images, a default start page and a redirection page into the newly created application. If set to false, no content files are copied into the new application tree. See also the Demo Pages section. |
| turbine.app.torque.use.idtable | Yes | true | If true, the all torque related goals will also build SQL code for the ID table which is used by the Torque ID Broker to generate unique IDs. If you use a different ID generation scheme (e.g. sequences), you can set this property to false and remove all id-table related files from the schema directory. |
| turbine.plugin.mode | Yes | normal | Selects the development mode for your application. |
| turbine.plugin.inplace.dir | Yes | . | Selects the location of the web application tree relative to to the root of your application when using inplace development. |
| turbine.setup.properties | Yes | setup.properties | Selects the properties file which is loaded to configure the turbine:setup goal. |
| Plugin | Property | Optional? | Default value | Description |
|---|---|---|---|---|
| appserver | maven.appserver.name | Yes | tomcat | Type of the application server used for testing and/or deploying of the application |
| torque | torque.database | Yes | postgresql | Sets the database type that this application will use |
| torque | torque.database.driver | Yes | not set | Set the database driver class |
| torque | torque.database.user | Yes | not set | Set the database user for connecting |
| torque | torque.database.password | Yes | not set | Set the database password for connecting |
| torque | torque.database.buildUrl | Yes | not set | JDBC-URI which can be used for creating tables and inserting data into the database |
| torque | torque.database.createUrl | Yes | not set | JDBC-URI which can be used by the Torque plugin to connect to the database engine to create the requested database. |
These properties are used at setup time and get copied into the M.E.T.A. generated project.properties file. They're used by various M.E.T.A. goals and can be changed to modify the behaviour of the plugin goals.
| Property | Optional? | Default value | Description |
|---|---|---|---|
| turbine.app.package | Yes | org.apache.turbine.app.${turbine.app.name} | The Java package of the new application. |
| turbine.app.om.name | Yes | ${turbine.app.name} | Name of the Torque datasource for application data. |
| turbine.app.om.package | Yes | ${turbine.app.package}.om | Package for the OM classes to be used for application data. |
| turbine.app.om.security.name | Yes | ${turbine.app.om.name} | Name of the Torque datasource which contains the Turbine security tables (users, groups, roles, permissions) |
| turbine.app.om.security.package | Yes | ${turbine.app.om.package} | Package for the OM classes to be used for security information. |
| turbine.plugin.base.dir | Yes | . | Relative location of the web application tree to the application root when using inplace development. |
| turbine.plugin.src.images | Yes | depends on development mode, see Directory tree reference | Directory where image files are kept. |
| turbine.plugin.src.pages | Yes | depends on development mode, see Directory tree reference | Directory where files that should go into the root of the web application are kept. |
| turbine.plugin.src.props | Yes | depends on development mode, see Directory tree reference | Directory where files that should go into the WEB-INF/classes directory of the web application are kept. |
| turbine.plugin.src.resources | Yes | depends on development mode, see Directory tree reference | Directory where misc. Turbine resources are kept. |
| turbine.plugin.src.schema | Yes | depends on development mode, see Directory tree reference | Directory where Torque schema files are kept. |
| turbine.plugin.src.scripts | Yes | depends on development mode, see Directory tree reference | Directory where Javascript files are kept. |
| turbine.plugin.src.style | Yes | depends on development mode, see Directory tree reference | Directory where cascading style sheets are kept. |
| turbine.plugin.src.templates | Yes | depends on development mode, see Directory tree reference | Directory where Velocity template files are kept. |
| turbine.plugin.src.conf | Yes | depends on development mode, see Directory tree reference | Directory where application and Turbine configuration files are kept. |
| turbine.plugin.src.java | Yes | depends on development mode, see Directory tree reference | Directory where the Java source tree is located. |
| turbine.plugin.src.test | Yes | depends on development mode, see Directory tree reference | Directory where Java source code for test classes is kept. |
| turbine.plugin.target.lib | Yes | depends on development mode, see Directory tree reference | Target directory for application libraries when using inplace development. |
| turbine.plugin.config.skip | Yes | false | If set to true, the configuration files from the turbine.plugin.src.conf location will be neither deployed nor added to the WAR file. |
| turbine.plugin.images.skip | Yes | false | If set to true, the files from the turbine.plugin.src.images location will be neither deployed nor added to the WAR file. |
| turbine.plugin.pages.skip | Yes | false | If set to true, the files from the turbine.plugin.src.pages location will be neither deployed nor added to the WAR file. |
| turbine.plugin.resources.skip | Yes | false | If set to true, the files from the turbine.plugin.src.resources location will be neither deployed nor added to the WAR file. |
| turbine.plugin.scripts.skip | Yes | false | If set to true, the files from the turbine.plugin.src.scripts location will be neither deployed nor added to the WAR file. |
| turbine.plugin.style.skip | Yes | false | If set to true, the files from the turbine.plugin.src.style location will be neither deployed nor added to the WAR file. |
| turbine.plugin.templates.skip | Yes | false | If set to true, the files from the turbine.plugin.src.templates location will be neither deployed nor added to the WAR file. |
| Plugin | Property | Optional? | Default value | Description |
|---|---|---|---|---|
| appserver | maven.appserver.home | Yes | not set | Defines the root directory of your application server used for testing and/or deploying of the application if you use a development mode that needs container deployment. |
| Property | Value | Description |
|---|---|---|
| turbine.target.dir | Deployment directory of your application | Available only in turbine:deploy postGoals to allow custom scripts to copy additional files to the deployment target. |