View Source

This page describes how to configure a Maven executable for a Task.

On this page:

Configuring a Maven Executable for a Task

To configure a Maven executable for a Task:

Navigate to the Task configuration for the Job (this will be the default Job if creating a new Plan).
Click the name of the desired Maven Task, or click 'Add Task' and then a Maven option (e.g. Maven 2.x) if creating a new Task.
In the 'Executable' dropdown, select the Maven executable that you wish to configure for this Task (e.g. "Maven 2"). The executable that you select will become one of the Task's capability requirements (and hence, one of the Job's requirements). For details, please see Configuring a Job's Requirements.
The screen will refresh to display the settings specific to Maven:
- 'Project File' (Optional, Maven 2.x or later only) — Enter the path to your Maven project file, relative to the working sub directory specified (below). If you do not specify this, Maven will use the pom.xml in the root of the working sub directory.
- 'Goal' — Specify the Maven goal that you want Bamboo to execute each time the source code changes. For example, clean test will run the Maven goal 'clean' followed by the Maven goal 'test'.
- 'Build JDK' — Choose a JDK from the list. The JDK that you select will become one of the Job's capability requirements. For details please see Configuring a Job's Requirements.
If required, update the system environment variables and working directory settings:

About the Maven Goal:
- You can use '-D' to define one or more JVM parameters. For example, -Djava.awt.headless=true will pass the parameter 'java.awt.headless' with a value of 'true'.
- Multiple maven goals can be specified with a space-delimited list.
- You can include variables (see Using Global or Build-specific Variables).
Specifying Generic JDK Requirements — You can specify generic JDK capabilities as requirements for your Task. You will need to configure a generic JDK capability first: