Clearly the shade option is easier today because it does not require to maintain 2 branches.
Do you have pointers on the removed methods? Most specs I reviewed were just 1-1. Anyway, it is a first step for us to enable people to play with jakarta package, we can still adjust things and if the fork is too big we would have to use jakarta branch but it would be a pain for no gain IMHO. If it is just about dropping a few methods we can add a shade transformer to do it IMHO. 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 mar. 28 avr. 2020 à 10:30, Mark Struberg <[email protected]> a écrit : > We also have a branch for jakartaee already. > > The question is which one is easier. There are btw slight differences. It > is NOT 1:1! Some methods got removed! > So I'd rather go the branch way. > > LieGrue, > strub > > Am 28.04.2020 um 07:37 schrieb Romain Manni-Bucau <[email protected]>: > > Hi everyone, > > Should we release jakarta artifacts? > Short term I'm just expecting a shade added to the default artifact since > for now it is 1-1 and for jakarta9 we would do the new bundle/artifact as > usual probably (seems the less costly compromise to me). > > If so (we do it now) I can take CDI SE stack + JSONB stack at my charge. > Happy to get help if anyone is interested. > > 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> > > >
