Any way to keep existing released jar compatible without keeping the module there? Saw some users still stucked to that :(
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-08-29 10:37 GMT+02:00 Mark Struberg <[email protected]>: > fine with 1.7.0. > > But then let's also get rid of JSF-1.2 support ;) > > Any objections? > > > LieGrue, > strub > > > > > > > On Monday, 29 August 2016, 10:27, Thomas Andraschko < > [email protected]> wrote: > > > +0 > > It's probably better to do a 1.7 instead 1.6.x release if we do this > > > > > > 2016-08-29 10:18 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > >> +0 (not sure it changes anything for us mid term but better to upgrade > >> since EOL are way overpassed) > >> > >> > >> Romain Manni-Bucau > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > >> <http://rmannibucau.wordpress.com> | Github <https://github.com/ > >> rmannibucau> | > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > >> <http://www.tomitribe.com> | JavaEE Factory > >> <https://javaeefactory-rmannibucau.rhcloud.com> > >> > >> 2016-08-29 10:16 GMT+02:00 Mark Struberg <[email protected]>: > >> > >> > Hi! > >> > > >> > I'm in the progress to update quite a few plugins in the OWB > > build. > >> > Most of them now require java7. And CDI-1.2 is also clearly EE7 > level. > >> > Which requires Java7. > >> > > >> > So I propose to upgrade trunk to Java7 as minimal requirement. > >> > > >> > Any objections? > >> > > >> > LieGrue, > >> > strub > >> > > >> > > >
