Maybe not drop EE7. I think all current app servers supporting Java EE 7 runs on Java 8.
But removing EE6, means for example that we no longer need BeanProvider and other specific code for EE6. So changing to Java 8 has quite some impact (but Java 8 is wanted I guess) and thus requires 2.x numbering. Rudy On 1 March 2018 at 15:50, John D. Ament <johndam...@apache.org> wrote: > IMHO to move to Java 8 we need to drop support for EE6/EE7. So to me that > says the next version is 2.0 not 1.9.x. > > There are some weld 1.1 versions that support this, but no testable AS7 > instance that we can check against. > > John > > On Thu, Mar 1, 2018 at 9:35 AM Cody Lerum <cody.le...@gmail.com> wrote: > > > +1 there is no reason for someone running Java 7 to expect new features > > from Deltaspike. > > > > On Feb 28, 2018 9:48 PM, "Mark Struberg" <strub...@yahoo.de.invalid> > > wrote: > > > > > Hi folks! > > > > > > Our build, etc in theory still runs with Java6. > > > As typical with ASF projects we make battle prooven projects for > > > production. > > > That means we take backward compatibility really serious. > > > > > > But I think it's finally time to up the game to Java8. > > > To indicate this I suggest to move from currently 1.8.x to 1.9.x. > > > > > > Note that all the rest will still be backward compatible with older > > > versions! > > > We also might still ship 1.8.2, 1.8.3, etc as Java7 compatible version > if > > > there is any necessity. > > > > > > Any objections? > > > > > > LieGrue, > > > strub > > >
