Maybe it should be, but I wanted to drop a note that about a month after December's decision to require Maven 3.6.3, I shifted onto an open source project that's been around for 10+ years, is actively backed by two large tech companies, and still depends on Maven 3.5.x in the continuous integration build. Bleah.
I've been trying to upgrade it, but so far without success. 3.5 seems baked pretty deeply into the Docker images or some other part of the CI infrastructure that isn't easy to change. This project could well be using Maven 3.5 for years to come. It's even possible we will rewrite the whole codebase in C++ before we manage to get past Maven 3.5. (I wish that was hyperbole. It's not.) I think we tend to overestimate how fast the installed base updates, whether it's JDKs (I got a bug report from someone still using Java 7 yesterday), Maven versions, operating systems, or pretty much anything else. None of us see more than a small fraction of the projects out there. It is very easy to look at that small fraction and draw conclusions that are falsified with a larger or different sample. I didn't know about this dependence on Maven 3.5 until I changed projects in January. I haven't seen 3.3 lately, but I wouldn't be surprised if it's still in use in multiple organizations, perhaps because it's what's installed by default in some old Linux distro that should also be retired but isn't. Absence of evidence is not evidence of absence, including when considering which Maven versions developers actively use. -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
