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:
- Getting Started Deploying Grails Apps
- Getting Started Deploying Ratpack Apps
- Getting Started Deploying Spring Apps
- Tips for Java Developers
- Configuring Service Connections for Grails
- Configuring Service Connections for Play
- Configuring Service Connections for Spring
- Cloud Foundry Eclipse Plugin
- Cloud Foundry Java Client Library
- BOSH Configured Custom Trusted Certificate Support
Buildpack Logging 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.Create a pull request or raise an issue on the source for this page in GitHub