Your error is a setup issue not a CDI error, you need to compile with cdi 1 API and run with cdi 2 API, there is no blocker to do it (we already swicth API jar depending the container).
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-12-20 14:18 GMT+01:00 John D. Ament <johndam...@apache.org>: > Hi, > > - No, you cannot build and test DS w/ Weld3 if your JVM is 1.6. However, > most of our builds are running 1.7 or 1.8 ATM (see also > https://builds.apache.org/view/A-D/view/DeltaSpike/job/ > DeltaSpike%20OWB%20JDK8/ > , > https://builds.apache.org/view/A-D/view/DeltaSpike/job/ > DeltaSpike%20Weld%202.4.1/ > ). > I would expect the Weld3 builds to run against Java 8 since that's the > required Weld version. > - RE DS2.0 it seems like every time this comes up, it gets turned > down/negatively spoken of. Would be good to get formal commitment to move > forward this way we can stop the back and forth. > > John > > On Tue, Dec 20, 2016 at 8:11 AM Thomas Andraschko < > andraschko.tho...@gmail.com> wrote: > > > Some months ago we talked about CDI 2.0 and that we would likely create a > > new branch for java8 and CDI 2.0 only -> DS 2.0. There we could also > > clenaup our API and remove stuff which is now available in CDI directly. > > > > However, it would be great if it would be possible that DS 1.x could work > > on both CDI1 and CDI2 (and Java7 ofc). > > >
