That is the idea for TomEE 7.1 yes.

You are correct regarding the MP Support for each version. We may try to bring 
MP 1.3 to TomEE 7, depending on the effort involved, but right now we will be 
focusing on TomEE 8.

Cheers,
Roberto

> On 27 Aug 2018, at 19:05, COURTAULT Francois <francois.courta...@gemalto.com> 
> wrote:
> 
> Does it mean that TomEE 7.1 will be released in a couple of days ?
> 
> What about the questions I have asked in my previous post ?
> - TomEE  7.1 will only come with  Config 1.1 MP, Fault Tolerance 1.0 MP and
> JWT propagation 1.0 MP, right ?
> - TomEE 8.0 will be full µProfile 1.3 certified: Config 1.2 MP updated
> and  Health Check 1.0 MP, Metrics 1.1 MP,  Open Tracing 1.0 MP, Open API 1.0 
> MP,
> Rest Client 1.0 MP added, right ?
> 
> Best Regards.
> 
> -----Original Message-----
> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
> Sent: lundi 27 août 2018 19:29
> To: us...@tomee.apache.org
> Cc: dev@tomee.apache.org
> Subject: Re: [RELEASE] TomEE 7.0.5
> 
> Correct, I'll delete and recreate on the next attempt to roll the release, 
> which will hopefully be later today.
> 
> Jon
> 
> On Mon, 27 Aug 2018, 18:22 David Blevins, <david.blev...@gmail.com> wrote:
> 
>>> On Aug 27, 2018, at 10:15 AM, COURTAULT Francois <
>> francois.courta...@gemalto.com> wrote:
>>> 
>>> Hello,
>>> 
>>> Thanks a lot for the feedback :-)
>>> 
>>> So it means that :
>>> - TomEE  7.1 will only embed Config 1.1, Fault Tolerance 1.0  and
>>> JWT
>> propagation 1.0, right ?
>>> - TomEE 8.0 will be full µProfile 1.3 certified: Config 1.2 updated
>> and  Health Check 1.0, Metrics 1.1 Open Tracing 1.0, Open API 1.0,
>> Rest Client 1.0 added, right ?
>>> 
>>> Why the availability of TomEE 7.1 hasn't been announced ?
>> 
>> 7.1 hasn't been released yet.  If there's a tag, it'll likely have to
>> be deleted.
>> 
>> 
>> -David
>> 
>> 
>>> 
>>> Best Regards.
>>> 
>>> -----Original Message-----
>>> From: Roberto Cortez [mailto:radcor...@yahoo.com.INVALID]
>>> Sent: lundi 27 août 2018 18:56
>>> To: us...@tomee.apache.org
>>> Cc: dev@tomee.apache.org
>>> Subject: Re: [RELEASE] TomEE 7.0.5
>>> 
>>> Hi Francois,
>>> 
>>> Right now, we are targeting MP 1.3 for TomEE 8. Unfortunately some
>>> of
>> the implementations required for MP 1.3 also required CDI 2.0 that is
>> only available in TomEE 8.
>>> 
>>> We added some of the specs from MP that were compatible with TomEE 7.
>> So, on TomEE 7 we support MP 1.2 without Metrics and Health.
>>> 
>>> TomEE 7.1 is being released and we are working to release TomEE 8.
>> Hopefully we have both released in the next few weeks.
>>> 
>>> Cheers,
>>> Roberto
>>> 
>>>> On 27 Aug 2018, at 17:07, COURTAULT Francois <
>> francois.courta...@gemalto.com> wrote:
>>>> 
>>>> Hello Jonathan,
>>>> 
>>>> Regarding 7.1.x vs 8, have you taken any decision ? (eg focus only
>>>> on
>> TomEE 8) When, according to you, could we expect to get a TomEE
>> µProfile
>> 1.3 certified ?
>>>> 
>>>> Little update, if I look at the Github repo, it seems that 7.1.0
>>>> has
>> been released or is in the process to be released soon, right ?
>>>> What is the µProfile version supported by this release ? 1.3 ?
>>>> 
>>>> Best Regards.
>>>> 
>>>> -----Original Message-----
>>>> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
>>>> Sent: lundi 23 juillet 2018 15:29
>>>> To: us...@tomee.apache.org
>>>> Cc: dev@tomee.apache.org
>>>> Subject: Re: [RELEASE] TomEE 7.0.5
>>>> 
>>>> We're actively working on it.
>>>> 
>>>> Jon
>>>> 
>>>> On Mon, Jul 23, 2018 at 2:27 PM, COURTAULT Francois <
>> francois.courta...@gemalto.com> wrote:
>>>> 
>>>>> Hello Jonathan,
>>>>> 
>>>>> Thanks for the clarification and good to hear that this version is
>>>>> certified on Java 9 :-) As the Java release cycle has been speed
>>>>> up, I would expect TomEE and Tomcat to support this new Java
>>>>> release cycle and, as Java 11 (LTS version) is coming, I would
>>>>> expect to be able to get a TomEE version, compatible with Java 11,
>>>>> right after this one would be released.
>>>>> 
>>>>> Best Regards.
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
>>>>> Sent: lundi 23 juillet 2018 15:20
>>>>> To: us...@tomee.apache.org
>>>>> Cc: dev@tomee.apache.org
>>>>> Subject: Re: [RELEASE] TomEE 7.0.5
>>>>> 
>>>>> Hi Francois
>>>>> 
>>>>> With respect to MicroProfile, this is at the same level as 7.0.4 - i.e.
>>>>> 1.0. I'm expecting we'll do a release of TomEE 8 soon, which will
>>>>> have more MicroProfile functionality. This release is mostly
>>>>> maintenance, although both TomEE and the libraries inside should
>>>>> now support Java 9 (and possibly 10, although I've had less luck
>>>>> with 10). Its the first release with Java 9 support, and I'll be
>>>>> aiming to release more often than we previously have, so please do
>>>>> let us know
>> any issues you find.
>>>>> 
>>>>> Thanks for adding the summary of library updates - I had added
>>>>> that on the vote thread and forgot to copy it here.
>>>>> 
>>>>> Jon
>>>>> 
>>>>> On Mon, Jul 23, 2018 at 2:06 PM, COURTAULT Francois <
>>>>> francois.courta...@gemalto.com> wrote:
>>>>> 
>>>>>> Hello everyone,
>>>>>> 
>>>>>> Good :-) Is this one µProfile certified ? if yes which version ?
>>>>>> I don't see so much information in the delivery regarding what's
>>>>>> differ between this latest version and the previous one (7.0.4).
>>>>>> 
>>>>>> Quick analysis :
>>>>>> - Tomcat 8.5.32 (latest version) instead of Tomcat 8.5.20
>>>>>> - apache-cxf 3.1.15 instead of 3.1.13
>>>>>> - johnzon 1.0.1 instead of 1.0.0
>>>>>> - mbean-annotation-api 7.0.5 instead of 7.0.4
>>>>>> - openejb 7.0.5 instead of 7.0.4
>>>>>> - openjpa 2.4.3 instead of 2.4.2
>>>>>> - openwebbeans 1.7.5 instead of 1.7.4
>>>>>> - xbean 4.9 instead of 4.5
>>>>>> - xmlschema-core 2.2.3 instead of 2.2.2
>>>>>> 
>>>>>> Best Regards.
>>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com]
>>>>>> Sent: lundi 23 juillet 2018 12:38
>>>>>> To: dev@tomee.apache.org; us...@tomee.apache.org
>>>>>> Subject: [RELEASE] TomEE 7.0.5
>>>>>> 
>>>>>> Hi
>>>>>> 
>>>>>> I'm please to annouce the release of TomEE 7.0.5. It may take a
>>>>>> little while for binaries to sync to the various mirrors (but
>>>>>> please let me know if you're still having issues getting binaries
>>>>>> in 24-48
>> hours time).
>>>>>> 
>>>>>> The list of changes is here:
>>>>>> https://emea01.safelinks.protection.outlook.com/?url=
>>>>>> https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FTOMEE-
>>>>>> 2175%3Fjql%3Dproject%2520%253D%2520TOMEE%2520AND%2520(
>>>>>> status%2520%253D%2520Resolved%2520OR%2520status%2520%253D%
>>>>>> 2520CLOSED)%2520AND%2520fixVersion%2520%253D%25207.0.5%2520ORDER%
>>>>>> 252 0B Y%
>>>>>> 2520priority%2520DESC%252C%2520updated%2520DESC&amp;data=
>>>>>> 02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C7c27747457ae460771ed
>>>>>> 08d
>>>>>> 5f
>>>>>> 088
>>>>>> 6b72%7C37d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636679391074392
>>>>>> 407
>>>>>> &a
>>>>>> mp;
>>>>>> sdata=Zqe7nrAy4W3LktdFvOf595L9jLqDwiooeuL7WA%2FEjQc%3D&amp;reserv
>>>>>> ed=
>>>>>> 0
>>>>>> 
>>>>>> Kind Regards
>>>>>> 
>>>>>> Jon
>>>>>> ________________________________
>>>>>> This message and any attachments are intended solely for the
>>>>>> addressees and may contain confidential information. Any
>>>>>> unauthorized use or disclosure, either whole or partial, is
>> prohibited.
>>>>>> E-mails are susceptible to alteration. Our company shall not be
>>>>>> liable for the message if altered, changed or falsified. If you
>>>>>> are not the intended recipient of this message, please delete it
>>>>>> and notify the
>>>>> sender.
>>>>>> Although all reasonable efforts have been made to keep this
>>>>>> transmission free from viruses, the sender will not be liable for
>>>>>> damages caused by a transmitted virus.
>>>>>> 
>>>>> ________________________________
>>>>> This message and any attachments are intended solely for the
>>>>> addressees and may contain confidential information. Any
>>>>> unauthorized use or disclosure, either whole or partial, is prohibited.
>>>>> E-mails are susceptible to alteration. Our company shall not be
>>>>> liable for the message if altered, changed or falsified. If you
>>>>> are not the intended recipient of this message, please delete it
>>>>> and
>> notify the sender.
>>>>> Although all reasonable efforts have been made to keep this
>>>>> transmission free from viruses, the sender will not be liable for
>>>>> damages caused by a transmitted virus.
>>>>> 
>>>> ________________________________
>>>> This message and any attachments are intended solely for the
>>>> addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>>>> E-mails are susceptible to alteration. Our company shall not be
>>>> liable
>> for the message if altered, changed or falsified. If you are not the
>> intended recipient of this message, please delete it and notify the sender.
>>>> Although all reasonable efforts have been made to keep this
>> transmission free from viruses, the sender will not be liable for
>> damages caused by a transmitted virus.
>>>> ________________________________
>>>> This message and any attachments are intended solely for the
>>>> addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>>>> E-mails are susceptible to alteration. Our company shall not be
>>>> liable
>> for the message if altered, changed or falsified. If you are not the
>> intended recipient of this message, please delete it and notify the sender.
>>>> Although all reasonable efforts have been made to keep this
>> transmission free from viruses, the sender will not be liable for
>> damages caused by a transmitted virus.
>>> 
>>> ________________________________
>>> This message and any attachments are intended solely for the
>>> addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>>> E-mails are susceptible to alteration. Our company shall not be
>>> liable
>> for the message if altered, changed or falsified. If you are not the
>> intended recipient of this message, please delete it and notify the sender.
>>> Although all reasonable efforts have been made to keep this
>>> transmission
>> free from viruses, the sender will not be liable for damages caused by
>> a transmitted virus.
>> 
>> 
> ________________________________
> This message and any attachments are intended solely for the addressees and 
> may contain confidential information. Any unauthorized use or disclosure, 
> either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for 
> the message if altered, changed or falsified. If you are not the intended 
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free 
> from viruses, the sender will not be liable for damages caused by a 
> transmitted virus.

Reply via email to