Maven properties that are flagged read-only for command-line binding lead to warnings with Maven 4

[snicoll]

See #43596

Some of our Mojos have a POJO structure for some of the parameters. For instance, the spring-boot:build-image goal as an <image> property that contains sub-properties such as name and the like.

Maven does not allow to bind a property of a POJO from the command line. To workaround this issue, the only way we found was to declare the parameter again, but flag it read-only so that it doesn't show up in auto-completion.

Maven 4 now makes use of that read-only flag and outputs a warning. We need to figure out what to do to preserve the current behavior.

[mhalbritter]

This warning pops up on Maven 3.9.9, too.

IntelliJ doesn't care about the readonly flag at all. It auto-suggests, when typing "image":

• image (readonly = false)
• imageName (readonly = true)
• imageBuilder (readonly = true)
• imagePlatform (readonly = true)
• runImage (readonly = true)

So from an IntelliJ auto-complete standpoint we can remove the readonly flags.

However, using mvn help:describe -Dplugin=org.springframework.boot:spring-boot-maven-plugin -Ddetail shows:

    image
      Image configuration, with {@code builder}, {@code runImage}, {@code
      name}, {@code env}, {@code cleanCache}, {@code verboseLogging}, {@code
      pullPolicy}, and {@code publish} options.

and no imageName, imageBuilder etc. So it doesn't show readonly = true @Parameters to the user.

I investigated a bit but couldn't find a different way to get the Image POJO to be bound.