Do you see something I missed? Do you have restrictions or edge cases maybe?
Le ven. 6 janv. 2023 à 13:13, Romain Manni-Bucau <rmannibu...@gmail.com> a écrit : > Hi, > > While there is an OSGi home for the spec (can move to karaf/smix/...) I'm > fine with that > > 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 ven. 6 janv. 2023 à 13:04, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> a écrit : > >> Hi all, >> >> Historically due to legal restrictions mainly, we created a bunch of spec >> jars for all APIs from almost the beginning of Java EE. >> >> Now that Jakarta is in Eclipse, I don't think there are restrictions to >> prevent us from using theM. >> >> I can think of a few exceptions >> >> - activation and mail because API/IMPL are mixed >> - same for Faces (we use spec and impl from MyFaces). >> >> I know we have some minor add-ons like a service locator for OSGi. Do we >> still need all of this? >> Who is maintaining that and the features XML file when they exist? >> >> From my window, except the few exceptions, we can terminate the spec jars >> and only maintain what we have if needed but encourage Apache projects to >> rely on Eclipse APIs instead. >> >> What do you think? >> Did I miss something? >> >> >> -- >> Jean-Louis Monteiro >> http://twitter.com/jlouismonteiro >> http://www.tomitribe.com >> > -- Jean-Louis
