Usage of Spring boot Gradle configuration name

[artemptushkin]

Spring Boot Gradle plugin has a special configuration developmentOnly which affects only development classpath

Currently:

• JIB uses by default on runtimeClasspath configuration
• Jib has a special Gradle extension that seems (according to the documentation only covers "devtools") which is not enough

Spring defines a special Gradle configuration productionRuntimeClasspath, see this comment for example.

This misaligned use causes issues in the production classpath which is hard to catch locally:

• locally we expect these dependencies to exist
• Spring disables them in tests so tests won't catch them too

Hence, the only way to catch them is to deploy the application.

Example issues:

• Spring devtools are exposed in the container image classpath
• Docker compose from spring-boot-docker-compose will be in the container runtime classpath too which is not expected and might cause issues (I got this issue)
• tl;dr any dependency supposed to be used with developmentOnly will be exposed*

Proposal options:

1. [Good option] Shall we, in case of Spring Boot apps, ("if spring boot") default it to productionRuntimeClasspath?
2. [No the best option] Shall the extension switch the configuration to productionRuntimeClasspath?

[manojks1999]

@artemptushkin can I work on this?

[artemptushkin]

@manojks1999 Thank you for your interest, fine with me, I'm not a maintainer but I can review as I know the project a bit