[FEATURE] Inherited `image` definitions

Description

In case of multiple projects using this plugin, it’s pretty difficult to centralize the configuration in a parent POM and reference only the required image blocks from child poms (pretty much the way dependencyManagement works). It would be nice to have a section where images can be pre-configured and then simply re-used inside other POMs. @rhuss we are willing to implement such a feature, would it make sense to have it?

[giannello]

@rhuss life was not nice to the project I was working on, and I completely forgot about this ticket. As nobody else seem to need this change, I’m closing it.

[awittha]

I didn’t see this originally, but I do have this use-case, for what it’s worth.

I work around the limitations by creating intermediate parent poms that use Maven’s <... combine.self="override"> and <... combine.children="override"> to ensure that only the relevant definitions are in-scope. Then, you just pick the correct parent pom and you’ve got your image definitions.

If I had a larger set of image definitions that I needed to work with, or needed to combine them in various (perhaps unknown 'till runtime) ways, this workaround wouldn’t work for me. My needs are simple enough that

Relying on the position of the images in the configuration …

has been sufficient, as the intermediate poms are “managed” and not exposed to end-users, so they are predictable enough.