Pushing a Java app with offline buildpack fails after the same app was already pushed with online buildpack

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Pushing a Java app with an offline buildpack fails after the same app was already pushed with online buildpack 

This is observed due to the application having once been ran with the online java buildpack. This causes an index.yml to be created in the application's cache. This cache takes precedence over all other caches (new buildpack's cache in this example). When the offline java buildpack is used, the index.yml in the buildpack is ignored because the old one still exists in the application's cache. 

Note: The same might apply for apps deployed with offline buildpack after attempt to deploy the same with online buildpack.

Environment

Product Version: 2.7

Resolution

• Delete the app
• Deploy the app with the new java offline buildpack

We do not encourage switching between online and offline buildpacks regularly.