Hi all, We discussed multiple times the plugin version locking but it is an issue for the ones involved in the default lifecycle since now when you create a new project you need 50 lines to lock versions (from my window the convention over configuration became a configuration over anything)...and then you locked versions so upgrading maven is harder than it was by the past.
There is a debate between: 1 we need to lock version to get the build deterministic 2 we shouldn't lock versions and stay aligned on the defaults within maven 1 is quite wrong since it also implicitly assume you do not change the maven version (otherwise it just doesnt work for the same reason you want to lock plugin versions) but 2 is not 100% perfect since it can hide the fact you do use another version. However we are lucky and have enforcer plugin which does solves it. So I wonder if we should revert the version locking warning when pom is without any build section for default plugins. I know a custom extensions can somehow replace a super pom and kind of solve it but you still need to define it which is still undesired to have a proper default "convention" setup IMHO. Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064>
