Hi all, Since maven 4 is actually ready to be live as a 4.0.0 can be (will not explain to all people used to releases that "0" are never perfect) I think it is time to agree on the way we structure our plugin repositories to embrace and promote it.
There are two main schools: 1. one branch for maven 3, one branch for maven 4: basically we fork ourselves 2. one single multimodule project and a thin maven 3 specific integration and maven 4 specific integration when relevant The nice thing with option 2 is that it is easier to ensure both branches are aligned, run the same test suite on both, ensure documentations are aligned and - the most important for me - ensure we do start promoting maven 4 cause we know maven 3 is not where plugin good practise will be by design (api being only in maven 4). Therefore my vote would be for 2 in a lazy mode (ie a plugin not having at all an active maven 4 branch/work doesn't need any action yet). Wdyt? 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> Javaccino <https://javaccino.dev/> founder (Java/.NET service - contact via linkedin)
