We could but -1; users can simple stay on 2.x Also moving it to own modules is much effort to create and maintain.
3.x. will be a break some applications of course but CDI is there since almost 10 years, EL even longer. Also JSP with JSF....? There is even no compatible component lib. Am Do., 11. Okt. 2018 um 14:33 Uhr schrieb Mark Struberg <[email protected] >: > +1 > > We could also make it plugable? > Havent looked into the code since some time. > But what about moving those things into an own optional jar? > > LieGrue, > strub > > > > Am 10.10.2018 um 17:08 schrieb Thomas Andraschko < > [email protected]>: > > > > javax.el is the replacement since ages ;) > > > > At least lesser Code, lesser jar size, less cluttered, netter > maintainability probably. > > > > > > Matthew Broadhead <[email protected]> schrieb am Mi., 10. > Okt. 2018, 16:57: > > sounds like a great idea. it may result in performance gain or at least > > making the newer code less cluttered. what replaces Faces EL? > > > > On 10/10/18 16:29, Thomas Andraschko wrote: > > > Hi all, > > > > > > i would like to start a discussion about MyFaces 3.0. > > > > > > Mojarra started with removing old code for Mojarra 3.0 like removing > > > the "long time deprecated" managed beans and faces EL. > > > > > > I probably have some free time during the cold months, so i would like > > > to start with those changes. Maybe already this month. > > > > > > The first steps are: > > > - move master to 2.3.x branch > > > - make master 3.0.x > > > - remove managed beans > > > - remove facelets EL > > > > > > As managed beans are removed and JSF goes "full CDI", does it make > > > sense to still support our internal SPI like InjectionProvider? I > > > don't think so. > > > > > > I think it's a good chance to cleanup the project in generell - AFAIR > > > 3.0 also removes support of JSPs. > > > We can of course discuss each part to cleanup later in a own thread. > > > > > > WDYT? > > > > > > Regards, > > > Thomas > > > > > > > > > > > > > > > > > > >
