Apologies for the unprecise and incorrect answer:
By default, the spring-boot-maven-plugin does not honour "provided", but includes every dependency.
I've tried out the linked "thin" extension, but that one did not work for me.
Coming back to my original post, the idea was right:
Use the PropertiesLauncher and let it point to some directories where your JARs live.
We need to trigger this launcher. This can be achieved for example via using the layout type "DIR" in the spring-boot-maven-plugin.
Additionally one needs to provide a config file "loader.properties" which contains a property pointing to the directory (or directories) holding the JARs.
In case we want to provide a Spring Boot Executable JAR which does not contain any or just some of the dependencies, we need to exclude the undesired ones.
Multiple solutions exist (use the out-of-the-box abilities to exclude them one-by-one, modify the Executable JAR after generating it, enhance the spring-boot-maven-plugin to filter by scope). I chose the last solution.
See the linked GIST for a complete listing.