A Cloud Foundry buildpack for running JVM-based applications including Grails, Groovy, Java Main, Play Framework, Spring Boot, and Servlet apps.
Cloud Foundry Java Buildpack is a specialized tool for deploying JVM-based applications to the Cloud Foundry platform. It automatically detects and configures the runtime environment for various Java frameworks, handling dependencies and system integration so developers can focus on their application code.
Developers and operators deploying JVM-based applications (Grails, Groovy, Java Main, Play Framework, Spring Boot, and Servlet) to Cloud Foundry. It is also for organizations needing to customize buildpack behavior for foundation-wide or application-specific tuning.
Developers choose it for its 'convention over configuration' philosophy, providing sensible defaults for most JVM applications while allowing extensive customization when needed. Its unique selling point is the extensive framework integration with over 35 frameworks for monitoring, security, profiling, and database connectivity, and flexible JRE selection including OpenJDK, Azul Zulu, SapMachine, and BYOL options like GraalVM and Oracle JRE.
Cloud Foundry buildpack for running Java applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically runs Grails, Groovy, Java Main, Play Framework, Spring Boot, and Servlet applications with minimal configuration, as shown in the extensive example documentation.
Includes over 35 frameworks for monitoring, security, profiling, and database connectivity, such as AppDynamics, New Relic, and PostgreSQL JDBC, detailed in the framework-specific docs.
Allows both operators and developers to override defaults via environment variables (e.g., JBP_DEFAULT_* for foundation-wide, JBP_CONFIG_* for app-specific), enabling fine-tuned control without code changes.
Supports customization through Git repository forking to add custom components or modify existing ones, with clear documentation on extending the buildpack.
Bring-Your-Own-License JREs like GraalVM or Oracle require forking the buildpack and editing manifest.yml, a more involved process compared to the deprecated Ruby approach.
The Go buildpack deprecates key Ruby features like JBP_CONFIG_COMPONENTS for JRE selection, forcing teams to rewrite deployment scripts and adapt to new environment variable patterns.
Self-contained offline packages can exceed 1 GB in size due to bundled dependencies, making distribution and storage cumbersome compared to leaner online alternatives.