toolbox:versions -DapplyToPom=true defines a new property in BOM instead of updating parent project

[jakub-bochenski]

See also mojohaus/versions#1200

I tried using toolbox as an alternative.
It's better in that it detects that the property should be upgraded.

But it defines a new property in child/BOM module instead of updating the property defined in parent module.

[cstamas]

Yup, applyToPom is still limited, especially when a whole reactor is to be observed... is still marked as "experimental".

It works for simple use cases like having a parent POM that already follows "best practices" for now...

[jakub-bochenski]

It works for simple use cases like having a parent POM that already follows "best practices" for now...

Care to elaborate what those best practices are? I thought my module structure already does follow best practices (There is a project attached to the versions issue)

[cstamas]

@jakub-bochenski could you put your reproducer into a git repo? It would be much easier to show.... but on a related note:
apache/maven-site#598 (comment)

[jakub-bochenski]

interesting, thanks!
so the gist of what I'm doing wrong seems to be:

In short: only external BOMs should be imported to reactor.

[cstamas]

Yes, Maven4 already warns you if you import a BOM within a reactor, and later versions will probably fail the build even.