Why Reference Application build is calling versions:update-properties?

I can see that the Check Modules task is doing a “mvn versions:update-properties -Pupdate-to-latest”. Doco for the versions plugin and link to the profile.

First question is: do we want that? Doesn’t it cause the build to be more unreliable, as we are actually testing something that wasn’t commited? Shall we automatically commit if we detect there’s a newer version? I don’t like the fact that we are now testing upgraded versions but releasing whatever it was commited before.

What about all those exclusions, are they still valid?

Can I get rid of the profile and just pluginManagement on the default profile?

1 Like

I think we should commit if there’s a newer version of a dependency.

1 Like