Regarding the warning message about "[JavaMain] WARN Dependency versions have passed end-of-support date: {"spring-boot - 3.2.5"=>"2025-12-31"}, an operator may prevent staging of this app"

Products

• VMware Tanzu Application Service
• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

After upgrading to Java Buildpack v4.82.0, you might hit the below warning message during staging applications if the dependency Spring Boot have passed the Commercial Support Date (EOL).

[JavaMain] WARN Dependency versions have passed end-of-support date: {"spring-boot - 3.2.5"=>"2025-12-31"}, an operator may prevent staging of this app.

Cause

Java Buildpack v4.82.0 introduced Application Compliance Verification

This feature allows operators to control Spring Boot applications that have Spring dependencies that have passed their Commercial Support Date (EOL). The default behavior logs a warning message during application staging, indicating the dependency, version, and the EOL date that has passed.

Resolution

• The default behavior logs a warning message during application staging, indicating the dependency, version, and the EOL date that has passed.

   [JavaMain]                       WARN  Dependency versions have passed end-of-support date: {"spring-boot - 3.2.5"=>"2025-12-31"}, an operator may prevent staging of this app
   Exit status 0
   Uploading droplet, build artifacts cache...
   Uploading droplet...
   Uploading build artifacts cache...
   Uploaded build artifacts cache (131B)
   Uploaded droplet (118.4M)
   Uploading complete

Waiting for app spring-music to start...

 

 

• Operators can choose to block these applications from staging by setting the following environment variable:
  • Environment variable can be specified in the applications manifest file

JBP_CONFIG_VERIFY_COMPLIANCE: '{ staging_disabled: true }'

• • Or add command line arguments containing the environment variable

cf set-env APP_name JBP_CONFIG_VERIFY_COMPLIANCE '{ staging_disabled: true }'

This causes applications with EOL dependency versions to fail during staging, and developers must upgrade to supported versions and redeploy. Commercial support dates for Spring boot projects can be found at https://spring.io/projects/spring-boot#support.

• As with other buildpack variables, operators can enable the above setting platform-wide, using the prefix JBP_DEFAULT_VERIFY_COMPLIANCE:

cf set-staging-environment-variable-group '{"JBP_DEFAULT_VERIFY_COMPLIANCE":"{ staging_disabled: true }"}'

 

Sample App logs for staging failed :

$ cf logs spring-music --recent

   2026-05-26T05:22:45.74+0000 [STG/0] ERR [JavaMain]                       WARN  Dependency versions have passed end-of-support date: {"spring-boot - 3.2.5"=>"2025-12-31"}, staging failed
   2026-05-26T05:22:45.74+0000 [STG/0] ERR [Buildpack]                      ERROR Finalize failed with exception #<RuntimeError: dependencies_out_of_support: ["spring-boot - 3.2.5 - 2025-12-31"]>
   2026-05-26T05:22:45.75+0000 [STG/0] ERR dependencies_out_of_support: ["spring-boot - 3.2.5 - 2025-12-31"]
   2026-05-26T05:22:45.76+0000 [STG/0] ERR Failed to compile droplet: Failed to run finalize script: exit status 1
   2026-05-26T05:22:45.77+0000 [STG/0] OUT Exit status 223
   2026-05-26T05:22:46.50+0000 [STG/0] OUT Cell c24b739c-###### stopping instance efdb9926-######
   2026-05-26T05:22:46.50+0000 [STG/0] OUT Cell c24b739c-###### destroying container for instance efdb9926-######
   2026-05-26T05:22:46.60+0000 [API/0] OUT Staging failed for build: efdb9926-######, app: spring-music, app_guid: 704a7d59-######, error id: BuildpackCompileFailed, buildpacks: [{name: java_buildpack_offline, buildpack_name: java, version: v4.90.0-offline-###java-buildpack#4f81459, output_metadata: {dependencies_out_of_support: [spring-boot - 3.2.5 - 2025-12-31]}}]
   2026-05-26T05:22:46.63+0000 [API/0] ERR Failed to stage build efdb9926-######: BuildpackCompileFailed - staging failed