I'd go for:
* 1.8.x: java7 + EE6This one is needed for older business applications. Yes,
there are still servers running on Java7.
1.9.x: java8 + EE6There are also still a lot of WebSphere-8.5.x and JBoss EAP-6
servers in production. Those got updates to Java8 but are still EE6! This is
the workarounds aren't that bad. it's just that we could drop more
reflection calls (similar to what we discussed for jdk8 and
java.util.Optional).
ok - i'll document details about the warnings during the bootstrapping
process (and if needed how to get rid of some of them).
regards,
gerhard
I have not a clear view of the workarounds which are made and how
'bad'/hacky they are. But when we don't have major complaints about it (now
or in the past) I would not invest too much time in a temporary version for
CDI 1.2.
so #3.
Rudy
On 3 April 2018 at 22:34, Romain Manni-Bucau
All work for me and the apps i work on since a few years.
Le 3 avr. 2018 22:17, "Thomas Andraschko" a
écrit :
> +1 for 3)
> the workarounds are really not that big...
>
> i would leave it as it is for now and start with DS 2.0 (= CDI2.0 only) the
> next months.
>
>
hi @ all,
since we will need to maintain v1.8.x for a while and it's too early for
using cdi 2.0 (for a while), we should discuss if we should have one branch
using cdi 1.2+.
it would allow to get rid of several workarounds (and the corresponding
warnings during the bootstrapping process).
we