Migrating Traditional Java Buildpack to Java Cloud Native Buildpack

Products

• VMware Tanzu Application Service

Issue/Introduction

Here are some notes when migrating from Traditional Java Buildpack to Java Cloud Native Buildpack

Resolution

Here are some items to notes when migrating from Traditional Java Buildpack to Java Cloud Native Buildpack

 

• Check your environment variables. Here are some examples of environment variables that need to changed

  JBP_CONFIG_OPEN_JDK_JRE (jre.version)            → BP_JVM_VERSION

  JBP_CONFIG_OPEN_JDK_JRE (memory_calculator.stack_threads)  →  BPL_JVM_THREAD_COUNT

  JAVA_OPTS                                         → JAVA_TOOL_OPTIONS

For a list of support environment variables in Java Cloud Native Buildpack, please see here.

 

•  Service Bindings

VCAP_SERVICES are fully compatible with Java Cloud Native Buildpack

User defined services are also supported with Java Cloud Native Buildpack

 

• Application Lifecycle
  
  Applications must be created as new applications to use Cloud Native Buildpacks. The application lifecycle cannot be changed for existing Traditional Java Buildpack applications. Existing applications using traditional buildpacks will continue to work unchanged, but to use CNB features, you must create new applications or redeploy existing applications as new apps.

 

For more info on installation and using Java Cloud Native Buildpack, please see our docs.