Since some libraries contain licenses that do not allow distribution, customers who want to run our software must get the libraries by themselves and add these to the spring boot application.
Previously, we added the spring boot uber jar to a container and used the PropertiesLauncher and the LOADER_PATH so that the customer can mount the library in the container and adapt the classpath.
Now that we want to switch for the image generation to buildpack, just like mvn spring-boot:build-image would do. As the application is unpacked in the image, it seems to me that the PropertiesLauncher and LOADER_PATH would no longer work.
What is the recommended way to add third party Java libraries to a buildback-built spring boot container?
You need to sign in to view this answers
