インデックス![]()
ダウンロード (PDF、HTML および XML 形式)
[Bamboo Knowledge Base Home]
Documentation for Bamboo 4.3.x. Documentation for other versions of Bamboo is available too. 
![]()
This page describes how to import a plan from a Maven 2 project.
Bamboo can check out and parse the pom.xml from a Maven 2 project, and create a new plan using the details from it. This feature is not available for Maven 1 projects.
To create a new plan from a Maven 2 pom.xml file:
pom.xml file.pom.xml file that are shown on the 'Confirm Plan Details' page.pom.xml depended on a non-Maven 2 builder. If you do need to specify a non-Maven 2 builder, refer to the '2. Configure tasks for the plan' section on Create a new plan.If you wish to configure more plan options, please refer to Editing a plan's configuration.
Screenshot: Importing a plan from Maven 2
Security Manager settings too strict — Please note, during the Maven import process, the project file (pom.xml or other specified by the user) is analysed using the maven-embedder library. The parent POM files will be examined in the local repository or downloaded from network repositories. In order to reuse Maven's credentials for the network repositories, Bamboo requires internal access to the maven-embedder. If your JVM's or web container's SecurityManager settings are too strict, this process will fail and you will see an error similar to the following in your Bamboo logs:
"Problem while initializing Maven Embedder. Probably Security Manager settings are too strict, refer to http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html"
If your imported Maven project file uses repositories that require credentials (i.e. not public or local), you will need to adjust the SecurityManager settings for your JVM or web container appropriately for the import to work.
fire.initial.build.for.manual.strategy to your bamboo.cfg.xml file as described in Configuring system properties.