spring-boot-maven-plugin sets imagePlatform even if it's empty

[johnasiano]

"A Docker image cannot be built with the spring-boot-maven-plugin:3.4.0 if Docker API version is less than 1.41. In particular, a Spring Boot project builds are failing in Bitbucket pipelines when no 'imagePlatform' option configured for the project with the following error

Using an empty tag in the pom.xml doesn't help as Maven, most probably, assigns an empty string to the corresp. Java property.

The proposed fix is to check the config property for both null and empty string values."

The above is from a pull request that I saw. The question that I was unable to get an answer to was, why would someone be using an API version less than 1.41?

Also in the pull request, the poster says that in particular, Spring Boot project builds are failing when no imagePlatform option is configured. I'm not sure in what scenarios someone would not configure the imagePlatform option. By default, in Spring Boot project builds, is the imagePlatform option not configured? Are people specifically putting an empty tag?

The pull request mentions that due to the empty tag, an empty string is assigned to the tag.

a91745a

Due to the code change, empty strings will now return False rather than True. What effect does this change have on Docker, spring-boot-maven, and the general workflow/environment that the pull request is operating in as a whole?

[philwebb]

The PR in question is #43424

@johnasiano I'm not sure I understand what's driving your questions. Are you facing an issue with the fix? I don't know why someone would choose to run a version less than 1.41, but we want to support them if they choose to do so.