The java-buildpack is a Cloud Foundry buildpack for running JVM-based applications. It is designed to run many JVM-based applications (Grails, Groovy, Java Main, Play Framework, Spring Boot, and Servlet) with no additional configuration, but supports configuration of the standard components, and extension to add custom components.
To use this buildpack specify the URI of the repository when pushing an application to Cloud Foundry:
cf push -b https://github.com/cloudfoundry/java-buildpackThe following are very simple examples for deploying the artifact types that we support.
The buildpack supports configuration and extension through the use of Git repository forking. The easiest way to accomplish this is to use GitHub's forking functionality to create a copy of this repository. Make the required configuration and extension changes in the copy of the repository. Then specify the URL of the new repository when pushing Cloud Foundry applications. If the modifications are generally applicable to the Cloud Foundry community, please submit a pull request with the changes.
To learn how to configure various properties of the buildpack, follow the "Configuration" links below. More information on extending the buildpack is available here.
- Design
- Security
- Standard Containers
- Standard Frameworks
- AppDynamics Agent (Configuration)
- Java Options (Configuration)
- MariaDB JDBC (Configuration)
- New Relic Agent (Configuration)
- Play Framework Auto Reconfiguration (Configuration)
- Play Framework JPA Plugin (Configuration)
- PostgreSQL JDBC (Configuration)
- Spring Auto Reconfiguration (Configuration)
- Spring Insight
- Standard JREs
- Extending
- Related Projects
To run the tests, do the following:
bundle install
bundle exec rakeInstalling Cloud Foundry on Vagrant is useful for privately testing new features.
Pull requests are welcome; see the contributor guidelines for details.
This buildpack is released under version 2.0 of the Apache License.