Skip to content
This repository
branch: master

Cloud Foundry Maven Plugin


Since Maven is one of the dominant build and deployment tools in the Java world, we made the core functionality of the Cloud Foundry cf command line tool also available to Maven users.


In order to get started you must as a minimum add the cf-maven-plugin to your project's pom.xml:


A complete configuration example for a web application

Following is a typical configuration example, which uses most of the available configuration parameters. Use cf:help to see a complete list of configuration options.


in settings.xml:


Command Line Usage


The following Maven goals are available for the Cloud Foundry Maven Plugin:

cf:apps List deployed applications.
cf:app Show details of an application.
cf:delete Delete an application.
cf:env Show an application's environment variables.
cf:help Show documentation for all available commands.
cf:push Push and optionally start an application.
cf:push-only Push and optionally start an application, without packaging.
cf:restart Restart an application.
cf:start Start an application.
cf:stop Stop an application.
cf:target Show information about the target Cloud Foundry service.
cf:logs Tail application logs.
cf:recentLogs Show recent application logs.
cf:scale Scale the application instances up or down.
cf:services Show a list of provisioned services.
cf:service-plans Show a list of available service plans.
cf:create-services Create services defined in the pom.
cf:delete-services Delete services defined in the pom.
cf:bind-services Bind services to an application.
cf:unbind-services Unbind services from an application.
cf:login Log in to the target Cloud Foundry service and save access tokens.
cf:logout Log out of the target Cloud Foundry service and remove access tokens.

Usage Examples

Show documentation for all available commands

$ mvn cf:help

List deployed applications

$ mvn cf:apps

Delete an application

$ mvn cf:delete [-Dcf.appname]

Show target service information

$ mvn cf:target

Scale the application instances up or down

$ mvn cf:scale [-Dcf.appname] [-Dcf.instances]

Push and optionally start an application

$ mvn cf:push [-Dcf.appname] [-Dcf.path] [-Dcf.url] [-Dcf.instances] [-Dcf.memory] []

Restart the application

$ mvn cf:restart [-Dcf.appname]

Start the application

$ mvn cf:start [-Dcf.appname]

Stop the application

$ mvn cf:stop [-Dcf.appname]

Sensible Defaults


As the same configuration parameters can be provided either through system properties, configuration elements in the the pom.xml and through the settings.xml file (username and password information only), the following precedence rules apply (starting with the highest precedence):

  1. System Properties e.g. mvn cf:start -Dcf.appname
  2. setting.xml parameters for username and password
  3. pom.xml Configuration parameters e.g. <configuration><appname>myApp</appname></configuration>
  4. pom.xml Properties e.g. <properties><cf.appname>myApp</cf.appname><properties>

INFO The implemented behavior deviates slightly from standard Maven behavior. Usually Maven configuration parameters in the pom take precedence over system properties passed in via the command line. Within the scope of the Cloud Foundry Maven Plugin, however, system properties passed in via e.g. -Dcf.appname take precedence over pom configuration parameters.

Additional certain configuration parameter will fall back to using default values in case no configuration value was provided:


  • appname: If no app name is specified, the Maven artifact id is being used
  • instances: Defaults to 1
  • no-start: Defaults to false
  • memory: Defaults to Cloud Controller value
  • diskQuota: Defaults to Cloud Controller value
  • healthCheckTimeout: Defaults to Cloud Controller value
  • path: Defaults to ${}/${}.war
  • url: Defaults to the appname and the default domain
  • server: Special parameter to tell Maven which server element in settings.xml holds the credentials for Cloud Foundry. Defaults to cloud-foundry-credentials

The parameters username, password, target, and space don't have default values and you are required to provide them.

Advanced Configuration

The Cloud Foundry Maven Plugin can be configured either by providing relevant information in the pom.xml file and/or via command line parameters (system properties). This allows users to chose the configuration path most appropriate to their business needs. In most cases though, we expect users to configure the static and non-security-sensitive parameters in the pom.xml file.

Security and Storing of Cloud Foundry Credentials

While it is possible to configure Cloud Foundry security credentials within the pom.xml file, this is discouraged as this makes it likely that credentials will be publicly visible. A better option is to configure credentials using system properties. However, even better, the security credentials for your Cloud Foundry instance can also be configured using the standard server XML configuration element ([]). This allows for keeping out security-sensitive information from the pom.xml file, yet eliminating the need to provide the security credential every time you interact with Cloud Foundry. In that case, the username and password information is stored in the settings.xml file, which is usually placed under ~/.m2/settings.xml (home directory). The following example illustrated the necessary configuration:

Plugin configuration in pom.xml:


The server configuration element is optional. If not explicitly set, its value will default to cloud-foundry-credentials:

Configuration of mycloudfoundry-instance in settings.xml:


As mentioned previously, you can also provide the user credentials through the following command line parameters instead:

  • cf.username
  • cf.password

e.g. by using:

$ mvn cf:info -Dcf.username=myusername -Dcf.password=s3cr3t

If the credentials are defined via the server element (in settings.xml) AND through the command line, then the command line parameter takes the precedence.

Another alternative is to use the login and logout goals to authenticate with a user name and password, and allow all other goals to use access tokens saved by login.

$ mvn cf:login -Dcf.username=myusername -Dcf.password=s3cr3t

After the login goal is executed in this way, it is not necessary to have a user name or password configured.

Finally, describing probably a rather rare use-case: If you have multiple Cloud Foundry specific server elements defined in your settings.xml, you can address those through command line parameters as well using:

  • cf.server (e.g. mvn push -Dcf.server=mycloudfoundry-instance)

HTTP Proxies

The Cloud Foundry Maven Plugin will honor the Maven HTTP proxy configuration when communicating with the target Cloud Foundry service. See for more information on configuring HTTP proxies in Maven.

If a proxy is configured in the Maven settings.xml, it will be used by the plugin unless the Cloud Foundry target URL is included in the nonProxyHosts section of the proxy configuration.

Self-signed SSL Certificates

Some Cloud Foundry deployments, such as those deployed using Pivotal CF, use a self-signed certificate for SSL connectivity. If you attempt to target a Cloud Foundry service that is using self-signed certificates, you may get an error containing the text peer not authenticated.

To instruct the Cloud Foundry Maven plugin to accept self-signed certificates from the Cloud Foundry target endpoint, add <trustSelfSignedCerts>true</trustSelfSignedCerts> to the plugin configuration block.


Changes from version 1.0.2 to 1.0.3

  • Changed cf:logs to tail logs from Loggregator
  • Added cf:recentLogs
  • Fixed defaulting of url

Changes from version 1.0.0 to 1.0.2

  • Added HTTP Proxy support for targeting CF platforms from behind a proxy
  • Added support for user-provided service instances
  • Added support for healthCheckTimeout and diskQuota application parameters
  • Removed defaulting of memory app setting to prefer the default configured in Cloud Controller
  • Added trustSelfSignedCerts plugin parameter

Changes from version 1.0.0.M4 to 1.0.0

  • Upgraded to cloudfoundry-client-lib 1.0.0
  • Removed v1 support and all v1 concepts (update goal, runtime and framework parameters)
  • Added support for buildpacks
  • Renamed goals and parameters for consistency with 'cf' and Cloud Foundry Gradle Plugin
  • Changed login and logout goals to save tokens to the file ~/.cf/tokens.yml instead of ~/.mvn-cf.xml, for compatibility with the cf CLI

Changes from version 1.0.0.M3 to 1.0.0.M4

  • Upgraded to cloudfoundry-client-lib 0.8.2
  • Modified the output from older grid style to cleaner column style
  • Added Cloud Controller v1 / v2 (cloud_controller_ng) detection
  • Added support for org and space in v2 (cloud_controller_ng)
  • Added support for push and delete app to v2 (cloud_controller_ng)
  • Added show log for v2 (cloud_controller_ng)
  • Added support for create-services for v2 (cloud_controller_ng)

Changes from version 1.0.0.M2 to 1.0.0.M3

  • Added support for one or more service child elements for the element. This allows to create and delete services. The required config options for a service are name and vendor with version and tier being optional.
  • Modified the cf:push goal to take the services configuration and create the services, if they don't exist, and bind them to the application.
  • Added cf:logs goal which shows the log files of the application specified in either the configuration parameter or in the pom file.
  • Added cf:services goal which shows the list of available services along with provisioned ones.
  • Added cf:create-services goal which creates services specified in the configuration parameter or in the pom file.
  • Added cf:delete-services goal which deletes the services created using the services configuration in the pom file.

Changes from version 1.0.0.M1 to 1.0.0.M2

  • Added Framework configuration parameter (-Dcf.framework) which allows to set the framework for the application. It defaults to spring.
  • Added ability to deploy not only war-files but also point to directories and deploy those
  • Added support for deployments of stand-alone applications by specifying standalone as the framework
  • Deprecated warfile as now you can deploy stand-alone applications as well. Behavior is equal to the path property.
  • Added path configuration property (-Dcf.path).
  • Added Runtime property (-Dcf.runtime). It defaults to 'java' but technically you could also use the Maven Plugin to deploy e.g. Node and Ruby applications.
  • Improved cf:info Maven goal. It will now show a list of available frameworks and system services, as well as a list of available runtimes*
  • instances property now defaults to 1.
Something went wrong with that request. Please try again.