You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Roberto Cortez <ra...@yahoo.com.INVALID> on 2018/11/19 15:46:34 UTC

TomEE 8 - Next steps

Hi folks, 

Following up our initial push to have a Milestone Release of TomEE 8, I think we need to figure out the remaining steps to a final version:

- Update MP specs to the latests and support at least MP 2.0 spec.
- Provide MP support for other TomEE flavours: Plus, Plume, etc.
- Implement Java EE Security API.

These are for me the main blockers.

I know there is a Java 9+ effort to provide TomEE with the latest Java support. I think that is still on the early stages and nobody can say for certain how long is that going to take, so I wouldn’t like to delay the final TomEE 8 release because of it.

Now, that doesn’t mean if need to wait a year or so for it. I know that historically TomEE release are like big bang and it is in our hand to change it and make it better. My point is that we can release a TomEE 9 version with Java 11 support in a few months. 

Any thoughts?

Cheers,
Roberto

Re: TomEE 8 - Next steps

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Probably worth a read:


http://tomee-openejb.979440.n4.nabble.com/VOTE-next-tomee-version-targetting-EE-7-td4674650.html
http://tomee-openejb.979440.n4.nabble.com/Java-EE-version-Alignment-Troubles-td4674796.html

And related if you still feel motivated by reading after these pages ;)

Le mar. 20 nov. 2018 00:16, Roberto Cortez <ra...@yahoo.com.invalid> a
écrit :

> Nevermind, that was just a discussion because I had the idea that the
> Jakarta EE version was going to reset. This is not the case, so doesn’t
> make sense anymore.
>
> > On 19 Nov 2018, at 23:08, exabrial12 <ex...@gmail.com> wrote:
> >
> > Roberto, I'd advise to stick to https://semver.org semantics:
> >
> > It's worth a read at the link, but:
> >
> > major.minor.patch
> >
> > * major is API breaking changes, so removing an API or class
> > * minor is adding a new API or feature, or marking a public API as
> > deprecated, in a non-breaking manner
> > * patch is bug fixing, non-breaking unless functionality was incorrect
> >
> >
> >
> >
> > --
> > Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
>

Re: TomEE 8 - Next steps

Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Nevermind, that was just a discussion because I had the idea that the Jakarta EE version was going to reset. This is not the case, so doesn’t make sense anymore.

> On 19 Nov 2018, at 23:08, exabrial12 <ex...@gmail.com> wrote:
> 
> Roberto, I'd advise to stick to https://semver.org semantics: 
> 
> It's worth a read at the link, but:
> 
> major.minor.patch
> 
> * major is API breaking changes, so removing an API or class
> * minor is adding a new API or feature, or marking a public API as
> deprecated, in a non-breaking manner
> * patch is bug fixing, non-breaking unless functionality was incorrect
> 
> 
> 
> 
> --
> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 8 - Next steps

Posted by exabrial12 <ex...@gmail.com>.
Roberto, I'd advise to stick to https://semver.org semantics: 

It's worth a read at the link, but:

major.minor.patch

* major is API breaking changes, so removing an API or class
* minor is adding a new API or feature, or marking a public API as
deprecated, in a non-breaking manner
* patch is bug fixing, non-breaking unless functionality was incorrect




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 8 - Next steps

Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Very well, sorry for misleading then.

At some point, I’ve got the impression it was going to be 1.0 and reset. I should have checked that.

> On 19 Nov 2018, at 22:13, Richard Monson-Haefel <mo...@gmail.com> wrote:
> 
> Jakarta EE is not going to reset back to 1.0. It's going to carry on from
> where Java EE left off. In fact, the first release of Jakarta EE will be
> version 8 and will be identical to Java EE 8.  Jakarta will then to go
> version 9, 10, etc.
> 
> On Mon, Nov 19, 2018 at 3:56 PM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
> 
>> Well that is the thing.
>> 
>> Some time ago, we aligned TomEE version to be the same as EE. Now, Jakarta
>> is going to reset the versions back to 1.0 as far as I know, so we don’t
>> have that link anymore, and we can’t really go back on versions, so I guess
>> we need to do something like:
>> 
>> Version x.y.z
>> 
>> x - major - EE API major change, major Java updates support, arquitectural
>> changes
>> y - middle - Changes that don’t fit either on x or z.
>> z - small - Regular releases, fixes, new features etc.
>> 
>> What do you think?
>> 
>>> On 19 Nov 2018, at 21:14, Thomas Andraschko <an...@gmail.com>
>> wrote:
>>> 
>>> +1
>>> better to use this versioning scheme - and wait for Jakarta EE9 to jump
>> to
>>> TomEE9.x
>>> 
>>> Am Mo., 19. Nov. 2018 um 21:38 Uhr schrieb exabrial12 <
>> exabrial@gmail.com>:
>>> 
>>>> What does everyone think about about small releases (8.0.x, 8.1.x,
>> 8.2.x)
>>>> with each Minor (middle) number adds a new API? Once we get to all the
>>>> desired API level we could issue an LTS (so declare that 8.6.x would be
>>>> like
>>>> Java11 support, MP, and JEE8, plus it'd be around for awhile). This
>> sort of
>>>> models what Java is doing anyway and what Ubuntu has been doing for
>>>> awhile.
>>>> 
>>>> I'd rather have a clear, but fast release cadence than the big bang
>> type of
>>>> releases we seem to fall into :) Thoughts?
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from:
>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>> 
>> 
>>

Re: TomEE 8 - Next steps

Posted by Richard Monson-Haefel <mo...@gmail.com>.
Jakarta EE is not going to reset back to 1.0. It's going to carry on from
where Java EE left off. In fact, the first release of Jakarta EE will be
version 8 and will be identical to Java EE 8.  Jakarta will then to go
version 9, 10, etc.

On Mon, Nov 19, 2018 at 3:56 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Well that is the thing.
>
> Some time ago, we aligned TomEE version to be the same as EE. Now, Jakarta
> is going to reset the versions back to 1.0 as far as I know, so we don’t
> have that link anymore, and we can’t really go back on versions, so I guess
> we need to do something like:
>
> Version x.y.z
>
> x - major - EE API major change, major Java updates support, arquitectural
> changes
> y - middle - Changes that don’t fit either on x or z.
> z - small - Regular releases, fixes, new features etc.
>
> What do you think?
>
> > On 19 Nov 2018, at 21:14, Thomas Andraschko <an...@gmail.com>
> wrote:
> >
> > +1
> > better to use this versioning scheme - and wait for Jakarta EE9 to jump
> to
> > TomEE9.x
> >
> > Am Mo., 19. Nov. 2018 um 21:38 Uhr schrieb exabrial12 <
> exabrial@gmail.com>:
> >
> >> What does everyone think about about small releases (8.0.x, 8.1.x,
> 8.2.x)
> >> with each Minor (middle) number adds a new API? Once we get to all the
> >> desired API level we could issue an LTS (so declare that 8.6.x would be
> >> like
> >> Java11 support, MP, and JEE8, plus it'd be around for awhile). This
> sort of
> >> models what Java is doing anyway and what Ubuntu has been doing for
> >> awhile.
> >>
> >> I'd rather have a clear, but fast release cadence than the big bang
> type of
> >> releases we seem to fall into :) Thoughts?
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>
>
>

Re: TomEE 8 - Next steps

Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Well that is the thing.

Some time ago, we aligned TomEE version to be the same as EE. Now, Jakarta is going to reset the versions back to 1.0 as far as I know, so we don’t have that link anymore, and we can’t really go back on versions, so I guess we need to do something like:

Version x.y.z

x - major - EE API major change, major Java updates support, arquitectural changes
y - middle - Changes that don’t fit either on x or z.
z - small - Regular releases, fixes, new features etc.

What do you think?

> On 19 Nov 2018, at 21:14, Thomas Andraschko <an...@gmail.com> wrote:
> 
> +1
> better to use this versioning scheme - and wait for Jakarta EE9 to jump to
> TomEE9.x
> 
> Am Mo., 19. Nov. 2018 um 21:38 Uhr schrieb exabrial12 <ex...@gmail.com>:
> 
>> What does everyone think about about small releases (8.0.x, 8.1.x, 8.2.x)
>> with each Minor (middle) number adds a new API? Once we get to all the
>> desired API level we could issue an LTS (so declare that 8.6.x would be
>> like
>> Java11 support, MP, and JEE8, plus it'd be around for awhile). This sort of
>> models what Java is doing anyway and what Ubuntu has been doing for
>> awhile.
>> 
>> I'd rather have a clear, but fast release cadence than the big bang type of
>> releases we seem to fall into :) Thoughts?
>> 
>> 
>> 
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>

Re: TomEE 8 - Next steps

Posted by Thomas Andraschko <an...@gmail.com>.
+1
better to use this versioning scheme - and wait for Jakarta EE9 to jump to
TomEE9.x

Am Mo., 19. Nov. 2018 um 21:38 Uhr schrieb exabrial12 <ex...@gmail.com>:

> What does everyone think about about small releases (8.0.x, 8.1.x, 8.2.x)
> with each Minor (middle) number adds a new API? Once we get to all the
> desired API level we could issue an LTS (so declare that 8.6.x would be
> like
> Java11 support, MP, and JEE8, plus it'd be around for awhile). This sort of
> models what Java is doing anyway and what Ubuntu has been doing for
> awhile.
>
> I'd rather have a clear, but fast release cadence than the big bang type of
> releases we seem to fall into :) Thoughts?
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Re: TomEE 8 - Next steps

Posted by exabrial12 <ex...@gmail.com>.
What does everyone think about about small releases (8.0.x, 8.1.x, 8.2.x)
with each Minor (middle) number adds a new API? Once we get to all the
desired API level we could issue an LTS (so declare that 8.6.x would be like
Java11 support, MP, and JEE8, plus it'd be around for awhile). This sort of
models what Java is doing anyway and what Ubuntu has been doing for awhile. 

I'd rather have a clear, but fast release cadence than the big bang type of
releases we seem to fall into :) Thoughts?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 8 - Next steps

Posted by Richard Monson-Haefel <mo...@gmail.com>.
+1

On Mon, Nov 19, 2018 at 10:40 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> I’ve got some feedback that people enjoyed having WebProfile +
> MicroProfile. If you strictly look just into the MP spec, sure you can
> develop an app with that, but most likely you will be requiring other stuff.
>
> Unless there is a high demand of having just a MP flavour, I think we are
> ok.
>
> Regarding Java 11, don’t get me wrong, I would love to have it there as
> well. I just think we should shift our mindset a little bit and provide
> more releases, with less features, so when the Java 11 work is done we can
> release it right away and people waiting for stuff don’t become
> uncomfortable because their feature didn’t make it into the big bang
> release, like Java is doing now.
>
> > On 19 Nov 2018, at 16:31, Daniel Cunha <da...@gmail.com> wrote:
> >
> > "Actually, kinda interested. I think we'd need to include MicroProfile in
> > TomEE Plus and TomEE Plume though."
> >
> > I'm totally agree.
> > Do we already have the CI running TomEE build with java 11?
> >
> > Em seg, 19 de nov de 2018 às 13:14, Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> escreveu:
> >
> >> Java 11 is definitely a priority. Personally, I'd rather get a regular
> >> milestone releases, rather than waiting for everything Java 11-wise to
> be
> >> in place.
> >>
> >> Jon
> >>
> >> On Mon, Nov 19, 2018 at 4:03 PM Thomas Andraschko <
> >> andraschko.thomas@gmail.com> wrote:
> >>
> >>> I'm not a commiter but a full java11 support is very important.
> >>> But probably all open stories are very important :D
> >>>
> >>>
> >>> Am Mo., 19. Nov. 2018 um 16:46 Uhr schrieb Roberto Cortez
> >>> <ra...@yahoo.com.invalid>:
> >>>
> >>>> Hi folks,
> >>>>
> >>>> Following up our initial push to have a Milestone Release of TomEE 8,
> I
> >>>> think we need to figure out the remaining steps to a final version:
> >>>>
> >>>> - Update MP specs to the latests and support at least MP 2.0 spec.
> >>>> - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> >>>> - Implement Java EE Security API.
> >>>>
> >>>> These are for me the main blockers.
> >>>>
> >>>> I know there is a Java 9+ effort to provide TomEE with the latest Java
> >>>> support. I think that is still on the early stages and nobody can say
> >> for
> >>>> certain how long is that going to take, so I wouldn’t like to delay
> the
> >>>> final TomEE 8 release because of it.
> >>>>
> >>>> Now, that doesn’t mean if need to wait a year or so for it. I know
> that
> >>>> historically TomEE release are like big bang and it is in our hand to
> >>>> change it and make it better. My point is that we can release a TomEE
> 9
> >>>> version with Java 11 support in a few months.
> >>>>
> >>>> Any thoughts?
> >>>>
> >>>> Cheers,
> >>>> Roberto
> >>>
> >>
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
>
>

Re: TomEE 8 - Next steps

Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
I’ve got some feedback that people enjoyed having WebProfile + MicroProfile. If you strictly look just into the MP spec, sure you can develop an app with that, but most likely you will be requiring other stuff.

Unless there is a high demand of having just a MP flavour, I think we are ok.

Regarding Java 11, don’t get me wrong, I would love to have it there as well. I just think we should shift our mindset a little bit and provide more releases, with less features, so when the Java 11 work is done we can release it right away and people waiting for stuff don’t become uncomfortable because their feature didn’t make it into the big bang release, like Java is doing now.

> On 19 Nov 2018, at 16:31, Daniel Cunha <da...@gmail.com> wrote:
> 
> "Actually, kinda interested. I think we'd need to include MicroProfile in
> TomEE Plus and TomEE Plume though."
> 
> I'm totally agree.
> Do we already have the CI running TomEE build with java 11?
> 
> Em seg, 19 de nov de 2018 às 13:14, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> escreveu:
> 
>> Java 11 is definitely a priority. Personally, I'd rather get a regular
>> milestone releases, rather than waiting for everything Java 11-wise to be
>> in place.
>> 
>> Jon
>> 
>> On Mon, Nov 19, 2018 at 4:03 PM Thomas Andraschko <
>> andraschko.thomas@gmail.com> wrote:
>> 
>>> I'm not a commiter but a full java11 support is very important.
>>> But probably all open stories are very important :D
>>> 
>>> 
>>> Am Mo., 19. Nov. 2018 um 16:46 Uhr schrieb Roberto Cortez
>>> <ra...@yahoo.com.invalid>:
>>> 
>>>> Hi folks,
>>>> 
>>>> Following up our initial push to have a Milestone Release of TomEE 8, I
>>>> think we need to figure out the remaining steps to a final version:
>>>> 
>>>> - Update MP specs to the latests and support at least MP 2.0 spec.
>>>> - Provide MP support for other TomEE flavours: Plus, Plume, etc.
>>>> - Implement Java EE Security API.
>>>> 
>>>> These are for me the main blockers.
>>>> 
>>>> I know there is a Java 9+ effort to provide TomEE with the latest Java
>>>> support. I think that is still on the early stages and nobody can say
>> for
>>>> certain how long is that going to take, so I wouldn’t like to delay the
>>>> final TomEE 8 release because of it.
>>>> 
>>>> Now, that doesn’t mean if need to wait a year or so for it. I know that
>>>> historically TomEE release are like big bang and it is in our hand to
>>>> change it and make it better. My point is that we can release a TomEE 9
>>>> version with Java 11 support in a few months.
>>>> 
>>>> Any thoughts?
>>>> 
>>>> Cheers,
>>>> Roberto
>>> 
>> 
> 
> 
> -- 
> Daniel "soro" Cunha
> https://twitter.com/dvlc_

Re: TomEE 8 - Next steps

Posted by Daniel Cunha <da...@gmail.com>.
"Actually, kinda interested. I think we'd need to include MicroProfile in
TomEE Plus and TomEE Plume though."

I'm totally agree.
Do we already have the CI running TomEE build with java 11?

Em seg, 19 de nov de 2018 às 13:14, Jonathan Gallimore <
jonathan.gallimore@gmail.com> escreveu:

> Java 11 is definitely a priority. Personally, I'd rather get a regular
> milestone releases, rather than waiting for everything Java 11-wise to be
> in place.
>
> Jon
>
> On Mon, Nov 19, 2018 at 4:03 PM Thomas Andraschko <
> andraschko.thomas@gmail.com> wrote:
>
> > I'm not a commiter but a full java11 support is very important.
> > But probably all open stories are very important :D
> >
> >
> > Am Mo., 19. Nov. 2018 um 16:46 Uhr schrieb Roberto Cortez
> > <ra...@yahoo.com.invalid>:
> >
> > > Hi folks,
> > >
> > > Following up our initial push to have a Milestone Release of TomEE 8, I
> > > think we need to figure out the remaining steps to a final version:
> > >
> > > - Update MP specs to the latests and support at least MP 2.0 spec.
> > > - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> > > - Implement Java EE Security API.
> > >
> > > These are for me the main blockers.
> > >
> > > I know there is a Java 9+ effort to provide TomEE with the latest Java
> > > support. I think that is still on the early stages and nobody can say
> for
> > > certain how long is that going to take, so I wouldn’t like to delay the
> > > final TomEE 8 release because of it.
> > >
> > > Now, that doesn’t mean if need to wait a year or so for it. I know that
> > > historically TomEE release are like big bang and it is in our hand to
> > > change it and make it better. My point is that we can release a TomEE 9
> > > version with Java 11 support in a few months.
> > >
> > > Any thoughts?
> > >
> > > Cheers,
> > > Roberto
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: TomEE 8 - Next steps

Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
No this is a different flavor.

It is based on webprofile though


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Nov 19, 2018 at 5:33 PM exabrial12 <ex...@gmail.com> wrote:

> Is MP support only in a WebProfile release currently?
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Re: TomEE 8 - Next steps

Posted by exabrial12 <ex...@gmail.com>.
Is MP support only in a WebProfile release currently?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 8 - Next steps

Posted by Jonathan Gallimore <jo...@gmail.com>.
Java 11 is definitely a priority. Personally, I'd rather get a regular
milestone releases, rather than waiting for everything Java 11-wise to be
in place.

Jon

On Mon, Nov 19, 2018 at 4:03 PM Thomas Andraschko <
andraschko.thomas@gmail.com> wrote:

> I'm not a commiter but a full java11 support is very important.
> But probably all open stories are very important :D
>
>
> Am Mo., 19. Nov. 2018 um 16:46 Uhr schrieb Roberto Cortez
> <ra...@yahoo.com.invalid>:
>
> > Hi folks,
> >
> > Following up our initial push to have a Milestone Release of TomEE 8, I
> > think we need to figure out the remaining steps to a final version:
> >
> > - Update MP specs to the latests and support at least MP 2.0 spec.
> > - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> > - Implement Java EE Security API.
> >
> > These are for me the main blockers.
> >
> > I know there is a Java 9+ effort to provide TomEE with the latest Java
> > support. I think that is still on the early stages and nobody can say for
> > certain how long is that going to take, so I wouldn’t like to delay the
> > final TomEE 8 release because of it.
> >
> > Now, that doesn’t mean if need to wait a year or so for it. I know that
> > historically TomEE release are like big bang and it is in our hand to
> > change it and make it better. My point is that we can release a TomEE 9
> > version with Java 11 support in a few months.
> >
> > Any thoughts?
> >
> > Cheers,
> > Roberto
>

Re: TomEE 8 - Next steps

Posted by Thomas Andraschko <an...@gmail.com>.
I'm not a commiter but a full java11 support is very important.
But probably all open stories are very important :D


Am Mo., 19. Nov. 2018 um 16:46 Uhr schrieb Roberto Cortez
<ra...@yahoo.com.invalid>:

> Hi folks,
>
> Following up our initial push to have a Milestone Release of TomEE 8, I
> think we need to figure out the remaining steps to a final version:
>
> - Update MP specs to the latests and support at least MP 2.0 spec.
> - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> - Implement Java EE Security API.
>
> These are for me the main blockers.
>
> I know there is a Java 9+ effort to provide TomEE with the latest Java
> support. I think that is still on the early stages and nobody can say for
> certain how long is that going to take, so I wouldn’t like to delay the
> final TomEE 8 release because of it.
>
> Now, that doesn’t mean if need to wait a year or so for it. I know that
> historically TomEE release are like big bang and it is in our hand to
> change it and make it better. My point is that we can release a TomEE 9
> version with Java 11 support in a few months.
>
> Any thoughts?
>
> Cheers,
> Roberto

Re: TomEE 8 - Next steps

Posted by Jonathan Gallimore <jo...@gmail.com>.
On Mon, Nov 19, 2018 at 3:54 PM Bruno Baptista <br...@gmail.com> wrote:

> Hi,
>
> I like the idea of more releases and incrementally add more features in
> a planned way.
>
> Also, what do you guys think of slimming the microprofile flavor by
> removing some non microprofile specs from it like JPA and such?
>

Actually, kinda interested. I think we'd need to include MicroProfile in
TomEE Plus and TomEE Plume though.


>
> Cheers
>
> Bruno Baptista
> http://twitter.com/brunobat_
>
>
> On 19/11/18 15:46, Roberto Cortez wrote:
> > Hi folks,
> >
> > Following up our initial push to have a Milestone Release of TomEE 8, I
> think we need to figure out the remaining steps to a final version:
> >
> > - Update MP specs to the latests and support at least MP 2.0 spec.
> > - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> > - Implement Java EE Security API.
> >
> > These are for me the main blockers.
> >
> > I know there is a Java 9+ effort to provide TomEE with the latest Java
> support. I think that is still on the early stages and nobody can say for
> certain how long is that going to take, so I wouldn’t like to delay the
> final TomEE 8 release because of it.
> >
> > Now, that doesn’t mean if need to wait a year or so for it. I know that
> historically TomEE release are like big bang and it is in our hand to
> change it and make it better. My point is that we can release a TomEE 9
> version with Java 11 support in a few months.
> >
> > Any thoughts?
> >
> > Cheers,
> > Roberto
>

Re: TomEE 8 - Next steps

Posted by Bruno Baptista <br...@gmail.com>.
Hi,

I like the idea of more releases and incrementally add more features in 
a planned way.

Also, what do you guys think of slimming the microprofile flavor by 
removing some non microprofile specs from it like JPA and such?

Cheers

Bruno Baptista
http://twitter.com/brunobat_


On 19/11/18 15:46, Roberto Cortez wrote:
> Hi folks,
>
> Following up our initial push to have a Milestone Release of TomEE 8, I think we need to figure out the remaining steps to a final version:
>
> - Update MP specs to the latests and support at least MP 2.0 spec.
> - Provide MP support for other TomEE flavours: Plus, Plume, etc.
> - Implement Java EE Security API.
>
> These are for me the main blockers.
>
> I know there is a Java 9+ effort to provide TomEE with the latest Java support. I think that is still on the early stages and nobody can say for certain how long is that going to take, so I wouldn’t like to delay the final TomEE 8 release because of it.
>
> Now, that doesn’t mean if need to wait a year or so for it. I know that historically TomEE release are like big bang and it is in our hand to change it and make it better. My point is that we can release a TomEE 9 version with Java 11 support in a few months.
>
> Any thoughts?
>
> Cheers,
> Roberto