@David OWB is still on 3.0.0-M3: https://github.com/apache/openwebbeans/blob/master/webbeans-tck-jakarta/pom.xml#L167
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 17 mars 2021 à 08:15, Mark Struberg <strub...@yahoo.de.invalid> a écrit : > Indeed, I did just run a full TomEE build with those TCKs enabled over > there. > > Will start the release NOW :D > > LieGrue, > strub > > > Am 17.03.2021 um 01:08 schrieb David Blevins <david.blev...@gmail.com>: > > > >> On Mar 16, 2021, at 9:49 AM, Mark Struberg <strub...@yahoo.de.INVALID> > wrote: > >> > >> oki, it is now configurable. So the worst thing you could do is to > overwrite the default in an openwebbeans.properties file inside TomEE. > > > > Everything looks good for a release from the TomEE side. Fire at will. > > > >> Btw, TomEE builds perfectly fine with the latest owb version and all > pre-activated TCKs enabled. > > > > I don't believe either of us are running the CDI 3.0 TCK in our main > builds, which is where the issue occurred. > > > > > > -David > > > > > >
