Re: Closing JIRA Issues

Ok good. I did not check myself, but I'll be trying to do the 7.1.x release soon if possible so at the same time I can have a look -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Jul 26, 2018 at 8:10 AM, Gurkan Erdogdu wrote: > Yes I did (and solved som

Re: TomEE 7.1 with MP

Everything should be merged and mistake fixed (wrong branch deleted) -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Jul 26, 2018 at 1:43 PM, Romain Manni-Bucau wrote: > Ok, > then AFAIK it will not be a "work" branch but just an aggregator branch so >

Re: TomEE 7.1 with MP

Ok, then AFAIK it will not be a "work" branch but just an aggregator branch so I see two good compromises: 1. use tomee 7.0 (we just add a mp module with tomee-maven-plugin Vn-1 to import MP impls and bundle it), no compile issue, tomee 7.0 stays java 7 and MP is aligned on java 8 2. we make 7.1 d

Re: TomEE 7.1 with MP

No. As far as I'm concerned its supported for as long as someone is willing to support it. I'm willing to support it, and I'm willing to support 1.7.x also. Jon On Thu, Jul 26, 2018 at 11:39 AM, Romain Manni-Bucau wrote: > Ok so means we drop tomee 7.0 support with next release? > > > Le jeu. 2

Re: TomEE 7.1 with MP

Ok so means we drop tomee 7.0 support with next release? Le jeu. 26 juil. 2018 12:20, Jonathan Gallimore < jonathan.gallim...@gmail.com> a écrit : > On Thu, Jul 26, 2018 at 11:18 AM, Mark Struberg > > wrote: > > > Yes, the following steps are now up to get done: > > > > 1.) Move the current mas

Re: TomEE 7.1.x branch mistake

On Thu, Jul 26, 2018 at 11:20 AM, Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > > Sorry about the noise > I'm sure we forgive you :)

TomEE 7.1.x branch mistake

Hey guys, While merging PR 138 from Roberto into branch tomee-7.1.x, I messed up with the names and created a new branch apache/tomee-7.1.x instead of pushing to tomee-7.1.x of the apache git repo. I'll be deleting the apache/tomee-7.1.x branch and push to the right one Sorry about the noise -

Re: TomEE 7.1 with MP

On Thu, Jul 26, 2018 at 11:18 AM, Mark Struberg wrote: > Yes, the following steps are now up to get done: > > 1.) Move the current master to a tomee-7.0.x branch > Done > 2.) Create a new tomee-7.1.x branch, upgrade to Java8 and add MicroProfile > JL doing > 2.) Move the tomee-8.x branch to

Re: TomEE 7.1 with MP

Yes, the following steps are now up to get done: 1.) Move the current master to a tomee-7.0.x branch 2.) Create a new tomee-7.1.x branch, upgrade to Java8 and add MicroProfile 2.) Move the tomee-8.x branch to master and get stuff rolling here as well. So I propose to upgrade our target to EE8 now

Re: TomEE 7.1 with MP

I think the 7.1.x was a proposal to have a stable TomEE with microprofile until we are ready to release something based on TomEE 8 -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Jul 26, 2018 at 12:07 PM, Romain Manni-Bucau wrote: > Hmm, did we get any

Re: TomEE 7.1 with MP

Hmm, did we get anything new compared to the thread "TomEE 7.1.x with Microprofile" to justify a 7.1 compared to directly jump to 8.0? Does it mean 7.0 is no more supported if we stick to only supportting 2 main branches? Romain Manni-Bucau @rmannibucau | Blog

Re: TomEE 7.1 with MP

Hey Roberto, Thanks for the PR. I have reviewed it and it looks good. So I'll proceed and merge. I'll see if I can throw a vote out for the 7.1.x +1 to switch master to 8.x as discussed. For TomEE 8.x we can try adding all the other microprofile implementations available at apache. Jean-Louis

Re: TomEE 7.1 with MP

On Thu, Jul 26, 2018 at 5:57 AM, Romain Manni-Bucau wrote: > Hi guys > > Didnt we plan to switch master to tomee 8 after the 7.0.5? We did agree that, and I'm happy to do that provided we can keep a branch for 7.0.x to maintain it. Unless anyone throws an objection on that in the next couple of