Re: New Status of TomEE 8

EE cert... +1 for after 8 is released. This conversation just >> reminded me of this thread quite some time ago now, with some views :) >> >> Status-of-TomEE-8 >> <http://tomee-openejb.979440.n4.nabble.com/Status-of-TomEE-8-td4683807.html> >> > >

Re: New Status of TomEE 8

> On 28 Feb 2019, at 01:04, David Blevins wrote: > >> On Feb 27, 2019, at 12:47 PM, j4fm wrote: >> >> On Jarkata EE cert... +1 for after 8 is released. This conversation just >> reminded me of this thread quite some time ago now, with some views :) >> &

New Status of TomEE 8

> On Feb 27, 2019, at 12:47 PM, j4fm wrote: > > On Jarkata EE cert... +1 for after 8 is released. This conversation just > reminded me of this thread quite some time ago now, with some views :) > > Status-of-TomEE-8 > <http://tomee-openejb.979440.n4.nabble.com/Status-o

Re: Status of TomEE 8

It is in since yesterday Le 5 mai 2018 15:53, "Matthew Broadhead" a écrit : > i saw MyFaces 2.3.1 was released. will that get update in 8.0? > > > On 05/05/18 14:18, Romain Manni-Bucau wrote: > >> We didnt upgrade the api yet and still uses validation 1.1 >> >>

Re: Status of TomEE 8

i saw MyFaces 2.3.1 was released.  will that get update in 8.0? On 05/05/18 14:18, Romain Manni-Bucau wrote: We didnt upgrade the api yet and still uses validation 1.1 Le 5 mai 2018 13:03, "cocorossello" a écrit : Hi, I just noticed that

Re: Status of TomEE 8

We didnt upgrade the api yet and still uses validation 1.1 Le 5 mai 2018 13:03, "cocorossello" a écrit : > Hi, > > I just noticed that javax.validation.ClockProvider and some methods related > to bean validation api 2.0 are missing in javaee-api-8.0-SNAPSHOT (I'm >

Re: Status of TomEE 8

Hi, I just noticed that javax.validation.ClockProvider and some methods related to bean validation api 2.0 are missing in javaee-api-8.0-SNAPSHOT (I'm using it with hibernate-validator 6.0). Is it an error? Thanks, Vicente. -- Sent from:

Re: Status of TomEE 8

Hi, If you can release the javaee-api 8.0 dependency I can start using tomee 8 in production, so I can give some feedback. I can release tomee in our private repository (I've already done it for tomee 7.0.5), so we can work comfortably with snapshots, but I don't know how to release that

Re: Status of TomEE 8

+1 for a next week release, no need of M1 or whatever marker in the name, just 8.0.0 is fine IMHO. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: Status of TomEE 8

+1 for april release.  i tried 8 with my projects and everything seemed fine On 19/04/18 11:26, Mark Struberg wrote: +1 And please note that we still have a few projects which are not yet fully EE8. E.g in BVal we are still working on it. Down to just a few failing TCK tests, but still.

Re: Status of TomEE 8

+1 And please note that we still have a few projects which are not yet fully EE8. E.g in BVal we are still working on it. Down to just a few failing TCK tests, but still. LieGrue, strub > Am 19.04.2018 um 08:17 schrieb Romain Manni-Bucau : > > A) without hesitation.

Re: Status of TomEE 8

A) without hesitation. After years of feedbacks, our state is that we have 2 kinds of users: - I dont care about the certification - Certification is mandatory for me to look at what you do Last category is clearly a subset of big companies and we lost them with EE 7 status so I think users just

Status of TomEE 8

> On Apr 17, 2018, at 9:57 PM, Romain Manni-Bucau wrote: > > What is blocking to release tomee 8? Nothing ;) Moving this over as it's probably a good "top level" topic to discuss. This will probably come to do "do we care about certification anymore" and that will