Think the question is: we'll we add any feature EE 6 users will start
working with? If yes we should stick to it, if not then just target EE
7 and move EE 6 in a maintenance branch.
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
2016-03-25 15:44 GMT+01:00 John D. Ament
-1 for dropping Java EE 6, we still have Java EE 6 users.
Also, as gerhard said, we don't gain much benefit from dropping it.
What about moving forward to DS 2.0 with Java EE 8 and Java SE 8 after the
release of Java EE 8?
2016-03-25 15:44 GMT+01:00 John D. Ament :
> IMHO we should target a maj
IMHO we should target a major version change if we're going to drop EE 6.
There's still some benefits to having EE 6, but they should start to die
down.
Maybe DeltaSpike 2.0 is EE 7 +?
John
On Fri, Mar 25, 2016 at 9:07 AM Christian Kaltepoth
wrote:
> I also think that we should keep to support
I also think that we should keep to support Java EE 6 for some time.
But +1 for dropping Java SE 6 support
2016-03-25 14:00 GMT+01:00 Rudy De Busscher :
> All,
>
> Most of my clients still work with Java EE 6 (on Java SE 7), so I think it
> is too early to abandon that version.
>
> +1 for settin
All,
Most of my clients still work with Java EE 6 (on Java SE 7), so I think it
is too early to abandon that version.
+1 for setting compile version to SE 7.
Regards
Rudy
On 25 March 2016 at 13:48, Gerhard Petracek wrote:
> hi @ all,
>
> imo the benefit is too limited.
> cdi 1.1 added some n
hi @ all,
imo the benefit is too limited.
cdi 1.1 added some nice parts, but mainly for users.
we would just drop the bv-module as well as some parts of the servlet
module.
the jsf-module already contains optional ee7 support (-> we would just get
rid of one small workaround).
for the rest the ben
Se 8 is surely too early (~1 year I think). +1 to drop ee6 from master.
Le 25 mars 2016 13:27, "Harald Wellmann" a écrit :
> Since John raised the question about Java SE 6 support, what about Java EE
> 6?
>
> Dropping support for Java EE 6/CDI 1.0 would simplify the code base
> significantly (a l
Since John raised the question about Java SE 6 support, what about Java
EE 6?
Dropping support for Java EE 6/CDI 1.0 would simplify the code base
significantly (a lot more so than moving from Java 1.6 to Java 1.7).
How about starting a new release line DeltaSpike 2.x targeting Java EE
7+ and
