Java Buildpack

Page last updated:

Use the Java buildpack with applications written in Grails, Play, Spring, or any other JVM-based language or framework.

See the following topics:

See the Java Buildpack Release Notes for information about specific versions. You can find the source for the Java buildpack on GitHub: https://github.com/cloudfoundry/java-buildpack

Buildpack and Application Logging

The buildpack only runs during the staging process, and therefore only logs staging information such as the downloaded components, configuration data, and work performed on your application by the buildpack.

The Java buildpack source documentation states the following:

  • The Java buildpack logs all messages, regardless of severity, to APP-DIRECTORY/.java-buildpack.log. The buildpack also logs messages to $stderr, filtered by a configured severity level.

  • If the buildpack fails with an exception, the exception message is logged with a log level of ERROR. The exception stack trace is logged with a log level of DEBUG. This prevents users from seeing stack traces by default.

Once staging completes, the buildpack stops logging. The Loggregator handles application logging.

Your application must write to STDOUT or STDERR for its logs to be included in the Loggregator stream. For more information, see the Application Logging in Cloud Foundry topic.

BOSH Custom Trusted Certificate Support

Java Buildpack versions 3.7 and later support BOSH configured custom trusted certificates.

Run the following command to configure support for this feature:

$ cf set-env APP-NAME JBP_CONFIG_CONTAINER_CERTIFICATE_TRUST_STORE '{enabled: true}'`

Alternatively, you can modify the buildpack by setting the enabled property to true in config/container_certificate_trust_store.yml. For more information, see the Java buildpack repository on GitHub.

Create a pull request or raise an issue on the source for this page in GitHub