Another maven dependency range not working as expected

I know this is a much discussed topic. There are severals pages with happy and sad endings.

I've read:

1. maven-dependency-range-does-not-work-as-expected
2. maven-version-ranges-do-not-behave-as-expected
3. Maven Version Range References
4. Legit but Useless: Maven Version Ranges Explained

All of these articles seems to talk about Hardcoded versions. What if the version is managed ? e.g: Sprigboot

Using the property

<maven-javadoc-plugin.version>[3.4.1)</maven-javadoc-plugin.version>

To override SpringBoot's one will result in a failure since it will try to use even ranges characters are version identifier attached image will show what I meant, and what maven is trying to do: