With the recent addition of the cf create-buildpack and cf update-buildpack commands, we’ve been looking into changes to how the Java Buildpack is deployed on Cloud Foundry. There is a move afoot to remove the buildpacks from the DEAs in favor of using those commands (with an automated initial install to preserve user-experience) and an outcome of this was the need to more easily create ‘packaged’ buildpacks. In the process of delivering these packages we also realized that we could also deliver “offline” buildpacks. To understand why “offline” buildpacks are interesting, it helps to understand why the buildpack is designed to look for dependencies on the Internet in the first place.
Stay Up To Date
Get the latest Cloud Foundry news and announcements
Cloud Foundry Summit Shanghai
Join us in Shangai December 2-3, 2015 as core contributors to the project and real world users discuss deep technical topics, engineering roadmap, community ecosystem and operational best practices.Register