If you think about such a change - Maven 4 should support both namespaces with warning about deprecating javax.inject. In this way developers will have more time and possibility to switch their plugins/extensions to new namespaces. Finally Maven 5 can support only new namespaces.
pon., 28 gru 2020 o 15:02 Romain Manni-Bucau <rmannibu...@gmail.com> napisał(a): > I agree javax will stay for years and doing any breaking change today would > just be bad for end users, that said we can already encourage plugins to > not use it and log a warning in maven plugin plugin. > For maven core we don't care much since we can change it when we want, it > will just impact extensions - and I agree again maven 5 can be the time to > do it. > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > Le lun. 28 déc. 2020 à 14:59, Michael Osipov <micha...@apache.org> a > écrit : > > > Am 2020-12-28 um 14:56 schrieb Markus KARG: > > > We are used to "import javax.inject.*" in Maven, but that namespace if > > dead > > > since Jakarta EE 9. Since November the new namespace is released > "import > > > jakarta.inject.*". I wonder if Maven 4 really still wants to stick with > > the > > > dead namespace instead, or whether it makes sense that we adopt the new > > > namespace now? > > > > That statement is very harsh. Both will co-exist for at least 10 years > > due to the massive amount of applications in companies. Maven tries to > > clean up stuff. I think this needs to be spared to Maven 5. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Sławomir Jaranowski
