Maven2
This page contains reference information about the Maven2 Build Runner fields.
Option | Description |
|---|---|
Build runner | Select Maven2 from the drop-down list. |
In the Goals field, you need to specify the sequence of Maven goals that you want TeamCity to execute. Some Maven goals can use version control systems, and, thus, they may become incompatible with some VCS checkout modes. If you want TeamCity to execute such goal:
| |
Specify path to the POM file relative to the Build Checkout Directory. By default, the property contains a pom.xml file. If you leave this field blank, the same value is put in this field. The path may also point to a subdirectory, and as such <subdirectory>/pom.xml is used. | |
Use this optional parameter to specify path to the distributive of your custom Maven. You do not need to specify this parameter, if you are going to use the Maven distributive that comes bundled with TeamCity (Maven 2.0.8). | |
Additional Maven command line parameters | Specify the list of command line parameters. Note that -h, -v, -B, -s, -f are ignored. |
Use this field to specify directories containing Build Artifact or file names as a comma-separated string. If a directory is specified its contents will be uploaded to the server. In version 3.1 this field is located on the 1.General Settings page. | |
The path to an alternative user settings file. It is equivalent to Maven's command line option -s or --settings. | |
The path to JDK Home is read from the *JAVA_HOME* environment variable or *JDK home* specified on the build agent if you leave this field empty. If these two values are not specified as well, TeamCity uses the JDK home on which the build agent process is started. | |
Specify JVM command line parameters, for example, maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build. Example: | |
Specify the Build Checkout Directory. Note that the build working directory correlates with |