I've only ever seen feedback of the nature that if people were willing to do 
the extra 7.1 work in addition to the TomEE 8 work, it wasn't a problem.

Note, just got off the MicroProfile hangout and there we've proposed to doing 
both a MicroProfile 1.4 and MicroProfile 2.0 release on June 6th.  The release 
contents would be the same with the exception of the minimum Java EE version; 
1.4 will remain at Java EE 7 and MicroProfile 2.0 will be Java EE 8.  Work 
would probably shift to MicroProfile 2.x afterwards, though future MicroProfile 
1.x releases could happen if component specs want to continue to cater to Java 
EE 7 or don't have any Java EE dependency at all.  That means MicroProfile will 
officially have two streams:

 - MicroProfile 1.x, Java EE 7, (potential TomEE 7.1)
 - MicroProfile 2.x, Java EE 8/Jakarta EE 8, TomEE 8


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

> On Apr 30, 2018, at 7:55 AM, Romain Manni-Bucau <[email protected]> wrote:
> 
> Hmm, can have missed something but didnt the outcome of the thread have
> been to work in tomee 8 branch (always better to avoid merges ;))?
> 
> 
> 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>
> 
> 2018-04-30 16:34 GMT+02:00 Jean-Louis Monteiro <[email protected]>:
> 
>> Hi community,
>> 
>> I have created a branch based on current master (aka TomEE 7.0.x) as
>> discussed a while back.
>> 
>> I have backported the microprofile JWT work from TomEE 8 branch.
>> The branch is https://github.com/jeanouii/tomee/tree/microprofile_backport
>> I have pushed what I have currently in there. I'll need to test more
>> deeply.
>> 
>> JLouis
>> 
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 

Reply via email to