Add back Paketo CA Certificates buildpack

[matthyx]

fixes #96

Summary

The CA Certificates buildpack was removed from the Java Native Image buildpack in v4.1.0. Recent version of the CNB lifecycle support buildpack API 0.5 and higher, so we can restore it.

Use Cases

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Matthias Bertschy (3bd2316)

[dmikusa]

Looks great, thanks. Merging in a sec.

One note for future reference only. The .github/workflows/update-*.yml files are auto-generated, so you don't technically need it here. In this case, the name of the file included should match what is generated by the automation, so worst case the automation will just update/overwrite what's here, which isn't a big deal.

[shresthaujjwal]

Any plans on releasing this change ?

[dmikusa]

Yes, but we are holding off on cutting a release for the moment. This is because the next release of the buildpack will also bump GraalVM to 21.1 and we have reports of compatibility problems with that version of GraalVM and Spring apps. The next release of this buildpack is planned to go out in tandem with the next release of Spring Native.

[matthyx]

Yes, but we are holding off on cutting a release for the moment. This is because the next release of the buildpack will also bump GraalVM to 21.1 and we have reports of compatibility problems with that version of GraalVM and Spring apps. The next release of this buildpack is planned to go out in tandem with the next release of Spring Native.

@dmikusa-pivotal 21.1 is out... any news on the release?

[dmikusa]

@matthyx - Still pending the Spring Native release, which was pushed back a little bit. If you want to use this now, you can specifically override the GraalVM version with pack build -b or if you're using Spring Boot 2.5, there's a similar configuration you can put in your Maven/Gradle config.

You could also check out main and run build your own java-native-image image. You need to run go get github.com/paketo-buildpacks/libpak/cmd/create-package, then create-package --destination ./out --version 5.4.0, then pack buildpack package --path ./out/ paketobuildpacks/java-native-image. You can then pack build -b paketobuildpacks/java-native-image and use the image you generated.

Sorry for the delay. We don't normally hold back this long. We just have a lot of Spring users and want to make sure they continue to have a smooth experience.

[matthyx]

no worries, thx for the update