The Spring Boot Maven plugin appears to replicate functionality already available in the pack CLI. Specifically, it:
Extracts the repackaged JAR and prepares it for buildpacks.
Contains logic for resolving the appropriate builder image.
Constructs and executes container-related commands.
This design introduces the need for Docker daemon configuration within the Maven plugin itself.
I’m trying to understand the rationale behind this approach. Was there a technical limitation or use case that required reimplementing this logic within the plugin rather than invoking the pack CLI directly (e.g., via a wrapper or Docker container)? Are there historical or architectural reasons documented anywhere that explain why the plugin doesn’t simply delegate to pack?
References to documentation, GitHub issues, or historical context around this design would be very helpful.
