You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2018/09/25 20:13:15 UTC
Re: TomEE 8 Release Notes Preview
Hey Community!
CodeOne (formerly JavaOne) is coming up at the end of October 22-25. We've been wanting to get TomEE 8 out anyway, but getting something out a week before code one would be an excellent opportunity to make some extra noise. Knowing us, that'd mean we'd need to start actually rolling and voting on releases pretty soon.
Roberto, I know you were heavy on TomEE 8 release at one point. Where did things leave off and are there any items people can help with?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Aug 28, 2018, at 9:02 AM, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>
> Hi,
>
> I’m trying to compile a list of things regarding the TomEE 8 Release. Right now, this is our preview for the Release Notes from JIRA:
>
> Bug
> • [TOMEE-2138] - MockitoExtension.Bean must implement Prioritized
> • [TOMEE-2167] - add <trim/> support for beans.xml
> • [TOMEE-2168] - upgrade maven-bundle-plugin to more recent version
> • [TOMEE-2172] - MDB instance not returned/discarded on tx timeout
> • [TOMEE-2206] - Support for Enum injection in Microprofile JWT
> New Feature
> • [TOMEE-2209] - MicroProfile 1.2 Support
> • [TOMEE-2210] - MicroProfile 1.3 Support
> • [TOMEE-2211] - MicroProfile 1.2 Support - Configuration 1.1
> • [TOMEE-2212] - MicroProfile 1.2 Support - Fault Tolerance 1.0
> • [TOMEE-2213] - MicroProfile 1.2 Support - JWT Propagation 1.0
> • [TOMEE-2214] - MicroProfile 1.2 Support - Health Check 1.0
> • [TOMEE-2215] - MicroProfile 1.2 Support - Metrics 1.0
> • [TOMEE-2216] - MicroProfile 1.3 Support - Config 1.2
> • [TOMEE-2217] - MicroProfile 1.3 Support - Metrics 1.1
> • [TOMEE-2218] - MicroProfile 1.3 Support - Rest Client 1.0
> • [TOMEE-2219] - MicroProfile 1.3 Support - Open API 1.0
> Improvement
> • [TOMEE-2195] - Compile Error in /src/main/java/org/apache/openejb/config/AnnotationDeployer
> • [TOMEE-2196] - keyStoreFile Property is Empty in Embedded Container
> • [TOMEE-2221] - Use a Jsonb aware JAX-RS Provider
> • [TOMEE-2222] - Enable create-tables for EclipseLink in Moviefun example
> • [TOMEE-2224] - update to apache-parent-21 for sha512
> Task
> • [TOMEE-2159] - TomEE8: JSF 2.3
> • [TOMEE-2160] - TomEE8: Servlet 4.0
> • [TOMEE-2174] - Nested parameters prevent EJB interceptor matching
> Dependency upgrade
> • [TOMEE-2171] - Upgrade to ActiveMQ 5.15.3
> • [TOMEE-2178] - TomEE8: Update to MyFaces 2.3.0 release
> • [TOMEE-2179] - tomcat 9.0.8
> • [TOMEE-2180] - johnzon 1.1.7
> • [TOMEE-2184] - MyFaces 2.3.1
> • [TOMEE-2186] - Upgrade CXF to 3.2.4
> • [TOMEE-2187] - Upgrade to XBean 4.9
> • [TOMEE-2207] - Update Bouncy Castle to 1.60
>
> Additionally, we have the following issue list associated to TomEE 8, that we need to update or decide if we need to do something with them for this release:
> • [TOMEE-2115] - TomEE-8 work
> • [TOMEE-2116] - Create javaee-api-8.0.0
> • [TOMEE-2117] - Rework ProcessObserverMethod integration
> • [TOMEE-2139] - org.apache.tomee.jul.handler.rotating.ArchivingTest broken in 2nd iteration
> • [TOMEE-2140] - retire or fix arquillian-jpa example
> • [TOMEE-2169] - Interceptor Bean injection does not work for EJBs
> • [TOMEE-2185] - Add MP-JWT support
> • [TOMEE-2227] - upgrade CXF to 3.2.6 and tomcat to 9.0.11
> • [TOMEE-2197] - openejb.xml <Deployments jar="..."/> does not work
>
> Also, I guess that a lot of work was done without creating issues, so everything that was done is not completely reflected in this list. We may need to create some issues for that.
>
> Thanks!
>
> Cheers,
> Roberto
>
>
Re: TomEE 8 Release Notes Preview
Posted by cocorossello <co...@gmail.com>.
It works in JDK 11 if compiled to java 10 and it doesn't work if compiled to
11. I guess that supported with upcoming ASM 7.0. Anyway if it runs in jdk
11 it's more than enough right now (at least for me)
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Re: TomEE 8 Release Notes Preview
Posted by David Blevins <da...@gmail.com>.
> On Sep 26, 2018, at 1:52 AM, Matthew Broadhead <ma...@nbmlaw.co.uk.INVALID> wrote:
>
> i thought TomEE 8 was going to target Java 8 first? a yum search on my CentOS server shows isn't even offering Java 11 yet. is TomEE 8 supposed to support 11 based on some specifications?
>
> although i suppose it would be eye catching to demo Java 11 support at a conference...
Right I think that's an important discussion point. I was imagining we'd still compile on Java 8, but work out any issues that'd prevent it from running in Java 11. I don't know if this is possible.
If this is a situation where we'd have to drop Java 8 support or there are complicated or non-optimal trade-offs, then I think we probably need to move ahead with Java 8 and discuss the impact of Java 11 a bit more.
-David
Re: TomEE 8 Release Notes Preview
Posted by Romain Manni-Bucau <rm...@gmail.com>.
g-validation will be released (vote sent) likely next week - likely without
javadoc love for this iteration until somebody finds time in the week-end.
Then bval 2.
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>
Le ven. 28 sept. 2018 à 12:17, Jonathan Gallimore <
jonathan.gallimore@gmail.com> a écrit :
> What's the status of the BVal release?
>
> On Fri, Sep 28, 2018 at 11:00 AM Roberto Cortez
> <ra...@yahoo.com.invalid>
> wrote:
>
> > Hi everyone,
> >
> > While we wait for the official BVal release, I plan do create a preview
> > release of TomEE 8 so we can start trying it out and hopefully speed up
> the
> > process. Please, let me know if anyone has any feedback.
> >
> > Cheers,
> > Roberto
> >
> > > On 27 Sep 2018, at 11:00, Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> > >
> > > For TomEE 8 and 7.1.x, definitely. We can upgrade it on earlier
> branches
> > > too, but it does require Java 8, so that would be the required minimum
> > for
> > > branches with this dependency. TomEE 7.0.x does still build with Java 7
> > and
> > > TomEE 1.7.x still builds with Java 6, but keeping Java at those levels
> is
> > > getting harder. Maybe its time to set those to Java 8.
> > >
> > > Jon
> > >
> > > On Wed, Sep 26, 2018 at 7:42 PM exabrial12 <ex...@gmail.com> wrote:
> > >
> > >> Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained
> an
> > >> important fix for client TLS hostname verification
> > >>
> > >>
> > >>
> > >> --
> > >> Sent from:
> > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>
> >
> >
>
Re: TomEE 8 Release Notes Preview
Posted by Jonathan Gallimore <jo...@gmail.com>.
What's the status of the BVal release?
On Fri, Sep 28, 2018 at 11:00 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:
> Hi everyone,
>
> While we wait for the official BVal release, I plan do create a preview
> release of TomEE 8 so we can start trying it out and hopefully speed up the
> process. Please, let me know if anyone has any feedback.
>
> Cheers,
> Roberto
>
> > On 27 Sep 2018, at 11:00, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
> >
> > For TomEE 8 and 7.1.x, definitely. We can upgrade it on earlier branches
> > too, but it does require Java 8, so that would be the required minimum
> for
> > branches with this dependency. TomEE 7.0.x does still build with Java 7
> and
> > TomEE 1.7.x still builds with Java 6, but keeping Java at those levels is
> > getting harder. Maybe its time to set those to Java 8.
> >
> > Jon
> >
> > On Wed, Sep 26, 2018 at 7:42 PM exabrial12 <ex...@gmail.com> wrote:
> >
> >> Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained an
> >> important fix for client TLS hostname verification
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>
>
>
Re: How to release snapshot dependencies in a TomEE release (Re:
TomEE 8 Release Notes Preview)
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Snapshots are ok for that, in particular since there is no strong activity
in tomee these days so the snapshot is "stable". It avoids the mess to fork
a project. It created issues with quartz and openjpa by the past when we
did so not sure users like that much at the end.
Very worse case we can push snapshots with a particular version like
8.0.0-SNAPSHOT-xxxx to mark them even more.
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>
Le dim. 30 sept. 2018 à 03:02, Roberto Cortez <ra...@yahoo.com.invalid>
a écrit :
> I think we should do a big push to have TomEE 8 out before Oracle Code One.
>
> With that said, we don’t have much time left, and since we still need to
> wait for a vote on BVal and TomEE I was trying to cut some time from the
> TomEE release if people would look at it now, and then when BVal is ready
> it should only be a matter of making the actual release.
>
> Cheers,
> Roberto
>
> > On 30 Sep 2018, at 01:08, David Blevins <da...@gmail.com> wrote:
> >
> > Agreed. If there's something that can be done to help them and the time
> to do it fits in the target window, that should be the first attempt.
> >
> > In a rare case a project may even accept help for the actual release.
> WebServices project made me committer in 2006 so I could cut Axis 1.4 that
> was needed by Geronimo 1.1. I've only experience that once, however.
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> >> On Sep 29, 2018, at 3:01 PM, Mark Struberg <st...@yahoo.de.INVALID>
> wrote:
> >>
> >> The primary way should imo ALWAYS to help the other projects we rely on
> to get the releases out.
> >> Falling back on a tomee internal release is only a last effort if the
> other projects are not responsible.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 28.09.2018 um 23:50 schrieb David Blevins <david.blevins@gmail.com
> >:
> >>>
> >>>> On Sep 28, 2018, at 3:00 AM, Roberto Cortez
> <ra...@yahoo.com.INVALID> wrote:
> >>>>
> >>>> While we wait for the official BVal release, I plan do create a
> preview release of TomEE 8 so we can start trying it out and hopefully
> speed up the process. Please, let me know if anyone has any feedback.
> >>>
> >>> As a community we've done ad-hoc releases other projects on a frequent
> basis when best case scenario (they release their code) doesn't pan out.
> >>>
> >>> I doug around to try and refresh my own memory.
> >>>
> >>> Pre-2013 we would use svn as a maven repo and push builds in with the
> version number suffixed with the svn version indicating the source. The
> groupIds were left the same:
> >>>
> >>> -
> https://svn.apache.org/viewvc/openejb/repo/org/apache/xbean/?pathrev=1432803
> >>>
> >>> This meant we had to include
> https://svn.apache.org/repos/asf/openejb/repo/ as a repository in the
> TomEE/OpenEJB pom.xml so we could release. When the project was renamed to
> tomee and that path changed to
> https://svn.apache.org/repos/asf/tomee/repo/ all those old builds broke.
> >>>
> >>> Post-2013 we would copy the source into our section of svn, update the
> groupId to ours with ".patch" appended, then add "nonfinal-<svnrevision>"
> to the version number and release it to mvn central.
> >>>
> >>> - svn log -v http://svn.apache.org/repos/asf/tomee/deps | less
> >>> -
> https://mvnrepository.com/artifact/org.apache.openejb.patch/openjpa-kernel/2.4.0-nonfinal-1598334
> >>>
> >>> This would be done as part of the TomEE release that needed them, such
> that the Nexus staging repo contained both TomEE 1.2.3 and say OpenJPA
> 2.4.0-nonfinal-1598334. When the project voted, it'd be voting on all the
> binaries. In your case it would be TomEE, BVal and Geronimo validation
> spec.
> >>>
> >>> You could potentially do a separate vote for BVal and Geronimo
> validation spec. If the project's get their releases up for a vote, great
> we use those releases for TomEE 8. If not, we have something to fall back
> on. The benefit of this is you would not have to keep rerolling these two
> each time you have to reroll TomEE 8 release binaries. I swore we did this
> once, but I couldn't find the vote thread as I don't recall exactly what
> artifact it was.
> >>>
> >>> Anyway, hope this helps. It likely should be added to our release
> process documentation.
> >>>
> >>>
> >>> -David
> >>>
> >>
> >
>
>
Re: How to release snapshot dependencies in a TomEE release (Re:
TomEE 8 Release Notes Preview)
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
I think we should do a big push to have TomEE 8 out before Oracle Code One.
With that said, we don’t have much time left, and since we still need to wait for a vote on BVal and TomEE I was trying to cut some time from the TomEE release if people would look at it now, and then when BVal is ready it should only be a matter of making the actual release.
Cheers,
Roberto
> On 30 Sep 2018, at 01:08, David Blevins <da...@gmail.com> wrote:
>
> Agreed. If there's something that can be done to help them and the time to do it fits in the target window, that should be the first attempt.
>
> In a rare case a project may even accept help for the actual release. WebServices project made me committer in 2006 so I could cut Axis 1.4 that was needed by Geronimo 1.1. I've only experience that once, however.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>> On Sep 29, 2018, at 3:01 PM, Mark Struberg <st...@yahoo.de.INVALID> wrote:
>>
>> The primary way should imo ALWAYS to help the other projects we rely on to get the releases out.
>> Falling back on a tomee internal release is only a last effort if the other projects are not responsible.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 28.09.2018 um 23:50 schrieb David Blevins <da...@gmail.com>:
>>>
>>>> On Sep 28, 2018, at 3:00 AM, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>>>>
>>>> While we wait for the official BVal release, I plan do create a preview release of TomEE 8 so we can start trying it out and hopefully speed up the process. Please, let me know if anyone has any feedback.
>>>
>>> As a community we've done ad-hoc releases other projects on a frequent basis when best case scenario (they release their code) doesn't pan out.
>>>
>>> I doug around to try and refresh my own memory.
>>>
>>> Pre-2013 we would use svn as a maven repo and push builds in with the version number suffixed with the svn version indicating the source. The groupIds were left the same:
>>>
>>> - https://svn.apache.org/viewvc/openejb/repo/org/apache/xbean/?pathrev=1432803
>>>
>>> This meant we had to include https://svn.apache.org/repos/asf/openejb/repo/ as a repository in the TomEE/OpenEJB pom.xml so we could release. When the project was renamed to tomee and that path changed to https://svn.apache.org/repos/asf/tomee/repo/ all those old builds broke.
>>>
>>> Post-2013 we would copy the source into our section of svn, update the groupId to ours with ".patch" appended, then add "nonfinal-<svnrevision>" to the version number and release it to mvn central.
>>>
>>> - svn log -v http://svn.apache.org/repos/asf/tomee/deps | less
>>> - https://mvnrepository.com/artifact/org.apache.openejb.patch/openjpa-kernel/2.4.0-nonfinal-1598334
>>>
>>> This would be done as part of the TomEE release that needed them, such that the Nexus staging repo contained both TomEE 1.2.3 and say OpenJPA 2.4.0-nonfinal-1598334. When the project voted, it'd be voting on all the binaries. In your case it would be TomEE, BVal and Geronimo validation spec.
>>>
>>> You could potentially do a separate vote for BVal and Geronimo validation spec. If the project's get their releases up for a vote, great we use those releases for TomEE 8. If not, we have something to fall back on. The benefit of this is you would not have to keep rerolling these two each time you have to reroll TomEE 8 release binaries. I swore we did this once, but I couldn't find the vote thread as I don't recall exactly what artifact it was.
>>>
>>> Anyway, hope this helps. It likely should be added to our release process documentation.
>>>
>>>
>>> -David
>>>
>>
>
Re: How to release snapshot dependencies in a TomEE release (Re:
TomEE 8 Release Notes Preview)
Posted by David Blevins <da...@gmail.com>.
Agreed. If there's something that can be done to help them and the time to do it fits in the target window, that should be the first attempt.
In a rare case a project may even accept help for the actual release. WebServices project made me committer in 2006 so I could cut Axis 1.4 that was needed by Geronimo 1.1. I've only experience that once, however.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Sep 29, 2018, at 3:01 PM, Mark Struberg <st...@yahoo.de.INVALID> wrote:
>
> The primary way should imo ALWAYS to help the other projects we rely on to get the releases out.
> Falling back on a tomee internal release is only a last effort if the other projects are not responsible.
>
> LieGrue,
> strub
>
>
>> Am 28.09.2018 um 23:50 schrieb David Blevins <da...@gmail.com>:
>>
>>> On Sep 28, 2018, at 3:00 AM, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>>>
>>> While we wait for the official BVal release, I plan do create a preview release of TomEE 8 so we can start trying it out and hopefully speed up the process. Please, let me know if anyone has any feedback.
>>
>> As a community we've done ad-hoc releases other projects on a frequent basis when best case scenario (they release their code) doesn't pan out.
>>
>> I doug around to try and refresh my own memory.
>>
>> Pre-2013 we would use svn as a maven repo and push builds in with the version number suffixed with the svn version indicating the source. The groupIds were left the same:
>>
>> - https://svn.apache.org/viewvc/openejb/repo/org/apache/xbean/?pathrev=1432803
>>
>> This meant we had to include https://svn.apache.org/repos/asf/openejb/repo/ as a repository in the TomEE/OpenEJB pom.xml so we could release. When the project was renamed to tomee and that path changed to https://svn.apache.org/repos/asf/tomee/repo/ all those old builds broke.
>>
>> Post-2013 we would copy the source into our section of svn, update the groupId to ours with ".patch" appended, then add "nonfinal-<svnrevision>" to the version number and release it to mvn central.
>>
>> - svn log -v http://svn.apache.org/repos/asf/tomee/deps | less
>> - https://mvnrepository.com/artifact/org.apache.openejb.patch/openjpa-kernel/2.4.0-nonfinal-1598334
>>
>> This would be done as part of the TomEE release that needed them, such that the Nexus staging repo contained both TomEE 1.2.3 and say OpenJPA 2.4.0-nonfinal-1598334. When the project voted, it'd be voting on all the binaries. In your case it would be TomEE, BVal and Geronimo validation spec.
>>
>> You could potentially do a separate vote for BVal and Geronimo validation spec. If the project's get their releases up for a vote, great we use those releases for TomEE 8. If not, we have something to fall back on. The benefit of this is you would not have to keep rerolling these two each time you have to reroll TomEE 8 release binaries. I swore we did this once, but I couldn't find the vote thread as I don't recall exactly what artifact it was.
>>
>> Anyway, hope this helps. It likely should be added to our release process documentation.
>>
>>
>> -David
>>
>
Re: How to release snapshot dependencies in a TomEE release (Re:
TomEE 8 Release Notes Preview)
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
The primary way should imo ALWAYS to help the other projects we rely on to get the releases out.
Falling back on a tomee internal release is only a last effort if the other projects are not responsible.
LieGrue,
strub
> Am 28.09.2018 um 23:50 schrieb David Blevins <da...@gmail.com>:
>
>> On Sep 28, 2018, at 3:00 AM, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>>
>> While we wait for the official BVal release, I plan do create a preview release of TomEE 8 so we can start trying it out and hopefully speed up the process. Please, let me know if anyone has any feedback.
>
> As a community we've done ad-hoc releases other projects on a frequent basis when best case scenario (they release their code) doesn't pan out.
>
> I doug around to try and refresh my own memory.
>
> Pre-2013 we would use svn as a maven repo and push builds in with the version number suffixed with the svn version indicating the source. The groupIds were left the same:
>
> - https://svn.apache.org/viewvc/openejb/repo/org/apache/xbean/?pathrev=1432803
>
> This meant we had to include https://svn.apache.org/repos/asf/openejb/repo/ as a repository in the TomEE/OpenEJB pom.xml so we could release. When the project was renamed to tomee and that path changed to https://svn.apache.org/repos/asf/tomee/repo/ all those old builds broke.
>
> Post-2013 we would copy the source into our section of svn, update the groupId to ours with ".patch" appended, then add "nonfinal-<svnrevision>" to the version number and release it to mvn central.
>
> - svn log -v http://svn.apache.org/repos/asf/tomee/deps | less
> - https://mvnrepository.com/artifact/org.apache.openejb.patch/openjpa-kernel/2.4.0-nonfinal-1598334
>
> This would be done as part of the TomEE release that needed them, such that the Nexus staging repo contained both TomEE 1.2.3 and say OpenJPA 2.4.0-nonfinal-1598334. When the project voted, it'd be voting on all the binaries. In your case it would be TomEE, BVal and Geronimo validation spec.
>
> You could potentially do a separate vote for BVal and Geronimo validation spec. If the project's get their releases up for a vote, great we use those releases for TomEE 8. If not, we have something to fall back on. The benefit of this is you would not have to keep rerolling these two each time you have to reroll TomEE 8 release binaries. I swore we did this once, but I couldn't find the vote thread as I don't recall exactly what artifact it was.
>
> Anyway, hope this helps. It likely should be added to our release process documentation.
>
>
> -David
>
How to release snapshot dependencies in a TomEE release (Re: TomEE 8
Release Notes Preview)
Posted by David Blevins <da...@gmail.com>.
> On Sep 28, 2018, at 3:00 AM, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>
> While we wait for the official BVal release, I plan do create a preview release of TomEE 8 so we can start trying it out and hopefully speed up the process. Please, let me know if anyone has any feedback.
As a community we've done ad-hoc releases other projects on a frequent basis when best case scenario (they release their code) doesn't pan out.
I doug around to try and refresh my own memory.
Pre-2013 we would use svn as a maven repo and push builds in with the version number suffixed with the svn version indicating the source. The groupIds were left the same:
- https://svn.apache.org/viewvc/openejb/repo/org/apache/xbean/?pathrev=1432803
This meant we had to include https://svn.apache.org/repos/asf/openejb/repo/ as a repository in the TomEE/OpenEJB pom.xml so we could release. When the project was renamed to tomee and that path changed to https://svn.apache.org/repos/asf/tomee/repo/ all those old builds broke.
Post-2013 we would copy the source into our section of svn, update the groupId to ours with ".patch" appended, then add "nonfinal-<svnrevision>" to the version number and release it to mvn central.
- svn log -v http://svn.apache.org/repos/asf/tomee/deps | less
- https://mvnrepository.com/artifact/org.apache.openejb.patch/openjpa-kernel/2.4.0-nonfinal-1598334
This would be done as part of the TomEE release that needed them, such that the Nexus staging repo contained both TomEE 1.2.3 and say OpenJPA 2.4.0-nonfinal-1598334. When the project voted, it'd be voting on all the binaries. In your case it would be TomEE, BVal and Geronimo validation spec.
You could potentially do a separate vote for BVal and Geronimo validation spec. If the project's get their releases up for a vote, great we use those releases for TomEE 8. If not, we have something to fall back on. The benefit of this is you would not have to keep rerolling these two each time you have to reroll TomEE 8 release binaries. I swore we did this once, but I couldn't find the vote thread as I don't recall exactly what artifact it was.
Anyway, hope this helps. It likely should be added to our release process documentation.
-David
Re: TomEE 8 Release Notes Preview
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Hi everyone,
While we wait for the official BVal release, I plan do create a preview release of TomEE 8 so we can start trying it out and hopefully speed up the process. Please, let me know if anyone has any feedback.
Cheers,
Roberto
> On 27 Sep 2018, at 11:00, Jonathan Gallimore <jo...@gmail.com> wrote:
>
> For TomEE 8 and 7.1.x, definitely. We can upgrade it on earlier branches
> too, but it does require Java 8, so that would be the required minimum for
> branches with this dependency. TomEE 7.0.x does still build with Java 7 and
> TomEE 1.7.x still builds with Java 6, but keeping Java at those levels is
> getting harder. Maybe its time to set those to Java 8.
>
> Jon
>
> On Wed, Sep 26, 2018 at 7:42 PM exabrial12 <ex...@gmail.com> wrote:
>
>> Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained an
>> important fix for client TLS hostname verification
>>
>>
>>
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>
Re: TomEE 8 Release Notes Preview
Posted by Jonathan Gallimore <jo...@gmail.com>.
For TomEE 8 and 7.1.x, definitely. We can upgrade it on earlier branches
too, but it does require Java 8, so that would be the required minimum for
branches with this dependency. TomEE 7.0.x does still build with Java 7 and
TomEE 1.7.x still builds with Java 6, but keeping Java at those levels is
getting harder. Maybe its time to set those to Java 8.
Jon
On Wed, Sep 26, 2018 at 7:42 PM exabrial12 <ex...@gmail.com> wrote:
> Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained an
> important fix for client TLS hostname verification
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
Re: TomEE 8 Release Notes Preview
Posted by exabrial12 <ex...@gmail.com>.
Is it possible to upgrade ActiveMQ to the latest 5.15.6? It contained an
important fix for client TLS hostname verification
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Re: TomEE 8 Release Notes Preview
Posted by cocorossello <co...@gmail.com>.
Oh, now I see that romain just upgraded. I will try with xbean 4.10
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Re: TomEE 8 Release Notes Preview
Posted by cocorossello <co...@gmail.com>.
Hi, just to share our experience, it works fine with java 11 runtime. If we
compile to java 11 (sourceCompatibility = 11) we get an error with xbean:
Caused by: java.lang.UnsupportedOperationException: null
at
org.apache.xbean.asm6.ClassVisitor.visitNestHostExperimental(ClassVisitor.java:158)
at org.apache.xbean.asm6.ClassReader.accept(ClassReader.java:541)
at org.apache.xbean.asm6.ClassReader.accept(ClassReader.java:391)
at
org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1168)
at
org.apache.xbean.finder.AnnotationFinder.<init>(AnnotationFinder.java:145)
at
org.apache.xbean.finder.AnnotationFinder.<init>(AnnotationFinder.java:158)
at
org.apache.openejb.config.FinderFactory$OpenEJBAnnotationFinder.<init>(FinderFactory.java:546)
at
org.apache.openejb.config.FinderFactory.newFinder(FinderFactory.java:267)
at org.apache.openejb.config.FinderFactory.create(FinderFactory.java:80)
But I think it may work upgrading to asm 6.2.1 in xbean.
(but we don't use bval neither openjpa)
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Re: TomEE 8 Release Notes Preview
Posted by Matthew Broadhead <ma...@nbmlaw.co.uk.INVALID>.
if it is close to ready for a release with 8 then i agree. is it
possible to start another branch targeting 11 support to see if it is
feasible before conference, or will that duplicate effort if it is split
from main branch?
On 26/09/18 10:58, Jonathan Gallimore wrote:
> There's no spec requirement, but lots of people keep asking me for it.
>
> Given the timescale, I'd be inclined to start a release with Java 8 support
> asap.
>
> Jon
>
> On Wed, 26 Sep 2018, 09:52 Matthew Broadhead,
> <ma...@nbmlaw.co.uk.invalid> wrote:
>
>> i thought TomEE 8 was going to target Java 8 first? a yum search on my
>> CentOS server shows isn't even offering Java 11 yet. is TomEE 8
>> supposed to support 11 based on some specifications?
>>
>> although i suppose it would be eye catching to demo Java 11 support at a
>> conference...
>>
>> On 25/09/18 23:17, David Blevins wrote:
>>> Speaking from my own perspective, if we could get 11 support into the
>> TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
>>> What is the best way for people to help?
>>>
>>>
>>
Re: TomEE 8 Release Notes Preview
Posted by Jonathan Gallimore <jo...@gmail.com>.
There's no spec requirement, but lots of people keep asking me for it.
Given the timescale, I'd be inclined to start a release with Java 8 support
asap.
Jon
On Wed, 26 Sep 2018, 09:52 Matthew Broadhead,
<ma...@nbmlaw.co.uk.invalid> wrote:
> i thought TomEE 8 was going to target Java 8 first? a yum search on my
> CentOS server shows isn't even offering Java 11 yet. is TomEE 8
> supposed to support 11 based on some specifications?
>
> although i suppose it would be eye catching to demo Java 11 support at a
> conference...
>
> On 25/09/18 23:17, David Blevins wrote:
> > Speaking from my own perspective, if we could get 11 support into the
> TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
> >
> > What is the best way for people to help?
> >
> >
>
>
Re: TomEE 8 Release Notes Preview
Posted by Matthew Broadhead <ma...@nbmlaw.co.uk.INVALID>.
i thought TomEE 8 was going to target Java 8 first? a yum search on my
CentOS server shows isn't even offering Java 11 yet. is TomEE 8
supposed to support 11 based on some specifications?
although i suppose it would be eye catching to demo Java 11 support at a
conference...
On 25/09/18 23:17, David Blevins wrote:
> Speaking from my own perspective, if we could get 11 support into the TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
>
> What is the best way for people to help?
>
>
Re: TomEE 8 Release Notes Preview
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Hi David,
This is our status for TomEE 8:
- We already have a successful green build.- We are waiting for some upstreams projects releases so we can remove the snapshots dependencies from TomEE- Right now, only BVal is missing. Mark and Romain are working on it.
In the meanwhile, I was trying to push for a JWT 1.1 version. I'll follow up in another email.
Cheers,Roberto On Tuesday, September 25, 2018, 10:27:40 PM GMT+1, Jonathan Gallimore <jo...@gmail.com> wrote:
Well, I think that is open for discussion, I'm not sure I have all the
answers... :)
I'm attempting to get the build going in J11, as that would include
actually running all the tests in the build on Java 11 which would be a
decent confidence boost. So far, that has basically entailed adding some
dependencies:
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.0</version>
</dependency>
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>2.3.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>javax.activation</groupId>
<artifactId>javax.activation-api</artifactId>
<version>1.2.0</version>
</dependency>
<dependency>
<groupId>org.jacorb</groupId>
<artifactId>jacorb</artifactId>
<version>3.9</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.rmi</groupId>
<artifactId>jboss-rmi-api_1.0_spec</artifactId>
<version>1.0.6.Final</version>
</dependency>
in a couple of places. Ideally I'd still want the build to work with Java
8, so I have done this in a profile. Changeset is here:
https://github.com/apache/tomee/compare/master...jgallimore:j11
I think we need some talk about actually including these dependencies in
the bundle. I was thinking of adding them in bin/ and trying to find some
way of adding them to the classpath if the JDK is 11 or above.
An initial validation of the approach would be welcome. If anyone has
experience in this area, some thoughts and discussion would be good to help
move it forward.
Jon
On Tue, Sep 25, 2018 at 10:17 PM David Blevins <da...@gmail.com>
wrote:
> Speaking from my own perspective, if we could get 11 support into the
> TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
>
> What is the best way for people to help?
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Sep 25, 2018, at 2:13 PM, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
> >
> > Question - we've merged some patches for Java 11, and to my knowledge
> > libraries we use are ok with Java 11 (although I haven't personally
> worked
> > through anything like all the testing I'd want to do). At the every least
> > there are some jars we'd need to include in the distro for Java 11 -
> JAXB,
> > Corba, RMI. Currently I'm trying to get 8.0.0 to _build_ with Java 11.
> Are
> > we looking to push 8.0.0 out as is, or would we want to push the Java 11
> > support and testing. Allowing a couple of weeks for votes, if we wanted
> to
> > push Java 11 in 8.0.0 in the CodeOne timeframe, I could use some help.
> >
> > Jon
> >
> > On Tue, Sep 25, 2018 at 9:13 PM David Blevins <da...@gmail.com>
> > wrote:
> >
> >> Hey Community!
> >>
> >> CodeOne (formerly JavaOne) is coming up at the end of October 22-25.
> >> We've been wanting to get TomEE 8 out anyway, but getting something out
> a
> >> week before code one would be an excellent opportunity to make some
> extra
> >> noise. Knowing us, that'd mean we'd need to start actually rolling and
> >> voting on releases pretty soon.
> >>
> >> Roberto, I know you were heavy on TomEE 8 release at one point. Where
> did
> >> things leave off and are there any items people can help with?
> >>
> >>
> >> --
> >> David Blevins
> >> http://twitter.com/dblevins
> >> http://www.tomitribe.com
> >>
> >>> On Aug 28, 2018, at 9:02 AM, Roberto Cortez
> <ra...@yahoo.com.INVALID>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I’m trying to compile a list of things regarding the TomEE 8 Release.
> >> Right now, this is our preview for the Release Notes from JIRA:
> >>>
> >>> Bug
> >>> • [TOMEE-2138] - MockitoExtension.Bean must implement Prioritized
> >>> • [TOMEE-2167] - add <trim/> support for beans.xml
> >>> • [TOMEE-2168] - upgrade maven-bundle-plugin to more recent
> version
> >>> • [TOMEE-2172] - MDB instance not returned/discarded on tx timeout
> >>> • [TOMEE-2206] - Support for Enum injection in Microprofile JWT
> >>> New Feature
> >>> • [TOMEE-2209] - MicroProfile 1.2 Support
> >>> • [TOMEE-2210] - MicroProfile 1.3 Support
> >>> • [TOMEE-2211] - MicroProfile 1.2 Support - Configuration 1.1
> >>> • [TOMEE-2212] - MicroProfile 1.2 Support - Fault Tolerance 1.0
> >>> • [TOMEE-2213] - MicroProfile 1.2 Support - JWT Propagation 1.0
> >>> • [TOMEE-2214] - MicroProfile 1.2 Support - Health Check 1.0
> >>> • [TOMEE-2215] - MicroProfile 1.2 Support - Metrics 1.0
> >>> • [TOMEE-2216] - MicroProfile 1.3 Support - Config 1.2
> >>> • [TOMEE-2217] - MicroProfile 1.3 Support - Metrics 1.1
> >>> • [TOMEE-2218] - MicroProfile 1.3 Support - Rest Client 1.0
> >>> • [TOMEE-2219] - MicroProfile 1.3 Support - Open API 1.0
> >>> Improvement
> >>> • [TOMEE-2195] - Compile Error in
> >> /src/main/java/org/apache/openejb/config/AnnotationDeployer
> >>> • [TOMEE-2196] - keyStoreFile Property is Empty in Embedded
> >> Container
> >>> • [TOMEE-2221] - Use a Jsonb aware JAX-RS Provider
> >>> • [TOMEE-2222] - Enable create-tables for EclipseLink in Moviefun
> >> example
> >>> • [TOMEE-2224] - update to apache-parent-21 for sha512
> >>> Task
> >>> • [TOMEE-2159] - TomEE8: JSF 2.3
> >>> • [TOMEE-2160] - TomEE8: Servlet 4.0
> >>> • [TOMEE-2174] - Nested parameters prevent EJB interceptor
> matching
> >>> Dependency upgrade
> >>> • [TOMEE-2171] - Upgrade to ActiveMQ 5.15.3
> >>> • [TOMEE-2178] - TomEE8: Update to MyFaces 2.3.0 release
> >>> • [TOMEE-2179] - tomcat 9.0.8
> >>> • [TOMEE-2180] - johnzon 1.1.7
> >>> • [TOMEE-2184] - MyFaces 2.3.1
> >>> • [TOMEE-2186] - Upgrade CXF to 3.2.4
> >>> • [TOMEE-2187] - Upgrade to XBean 4.9
> >>> • [TOMEE-2207] - Update Bouncy Castle to 1.60
> >>>
> >>> Additionally, we have the following issue list associated to TomEE 8,
> >> that we need to update or decide if we need to do something with them
> for
> >> this release:
> >>> • [TOMEE-2115] - TomEE-8 work
> >>> • [TOMEE-2116] - Create javaee-api-8.0.0
> >>> • [TOMEE-2117] - Rework ProcessObserverMethod integration
> >>> • [TOMEE-2139] -
> >> org.apache.tomee.jul.handler.rotating.ArchivingTest broken in 2nd
> iteration
> >>> • [TOMEE-2140] - retire or fix arquillian-jpa example
> >>> • [TOMEE-2169] - Interceptor Bean injection does not work for EJBs
> >>> • [TOMEE-2185] - Add MP-JWT support
> >>> • [TOMEE-2227] - upgrade CXF to 3.2.6 and tomcat to 9.0.11
> >>> • [TOMEE-2197] - openejb.xml <Deployments jar="..."/> does not
> work
> >>>
> >>> Also, I guess that a lot of work was done without creating issues, so
> >> everything that was done is not completely reflected in this list. We
> may
> >> need to create some issues for that.
> >>>
> >>> Thanks!
> >>>
> >>> Cheers,
> >>> Roberto
> >>>
> >>>
> >>
> >>
>
>
Re: TomEE 8 Release Notes Preview
Posted by Jonathan Gallimore <jo...@gmail.com>.
Well, I think that is open for discussion, I'm not sure I have all the
answers... :)
I'm attempting to get the build going in J11, as that would include
actually running all the tests in the build on Java 11 which would be a
decent confidence boost. So far, that has basically entailed adding some
dependencies:
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.0</version>
</dependency>
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>2.3.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>javax.activation</groupId>
<artifactId>javax.activation-api</artifactId>
<version>1.2.0</version>
</dependency>
<dependency>
<groupId>org.jacorb</groupId>
<artifactId>jacorb</artifactId>
<version>3.9</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.rmi</groupId>
<artifactId>jboss-rmi-api_1.0_spec</artifactId>
<version>1.0.6.Final</version>
</dependency>
in a couple of places. Ideally I'd still want the build to work with Java
8, so I have done this in a profile. Changeset is here:
https://github.com/apache/tomee/compare/master...jgallimore:j11
I think we need some talk about actually including these dependencies in
the bundle. I was thinking of adding them in bin/ and trying to find some
way of adding them to the classpath if the JDK is 11 or above.
An initial validation of the approach would be welcome. If anyone has
experience in this area, some thoughts and discussion would be good to help
move it forward.
Jon
On Tue, Sep 25, 2018 at 10:17 PM David Blevins <da...@gmail.com>
wrote:
> Speaking from my own perspective, if we could get 11 support into the
> TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
>
> What is the best way for people to help?
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Sep 25, 2018, at 2:13 PM, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
> >
> > Question - we've merged some patches for Java 11, and to my knowledge
> > libraries we use are ok with Java 11 (although I haven't personally
> worked
> > through anything like all the testing I'd want to do). At the every least
> > there are some jars we'd need to include in the distro for Java 11 -
> JAXB,
> > Corba, RMI. Currently I'm trying to get 8.0.0 to _build_ with Java 11.
> Are
> > we looking to push 8.0.0 out as is, or would we want to push the Java 11
> > support and testing. Allowing a couple of weeks for votes, if we wanted
> to
> > push Java 11 in 8.0.0 in the CodeOne timeframe, I could use some help.
> >
> > Jon
> >
> > On Tue, Sep 25, 2018 at 9:13 PM David Blevins <da...@gmail.com>
> > wrote:
> >
> >> Hey Community!
> >>
> >> CodeOne (formerly JavaOne) is coming up at the end of October 22-25.
> >> We've been wanting to get TomEE 8 out anyway, but getting something out
> a
> >> week before code one would be an excellent opportunity to make some
> extra
> >> noise. Knowing us, that'd mean we'd need to start actually rolling and
> >> voting on releases pretty soon.
> >>
> >> Roberto, I know you were heavy on TomEE 8 release at one point. Where
> did
> >> things leave off and are there any items people can help with?
> >>
> >>
> >> --
> >> David Blevins
> >> http://twitter.com/dblevins
> >> http://www.tomitribe.com
> >>
> >>> On Aug 28, 2018, at 9:02 AM, Roberto Cortez
> <ra...@yahoo.com.INVALID>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I’m trying to compile a list of things regarding the TomEE 8 Release.
> >> Right now, this is our preview for the Release Notes from JIRA:
> >>>
> >>> Bug
> >>> • [TOMEE-2138] - MockitoExtension.Bean must implement Prioritized
> >>> • [TOMEE-2167] - add <trim/> support for beans.xml
> >>> • [TOMEE-2168] - upgrade maven-bundle-plugin to more recent
> version
> >>> • [TOMEE-2172] - MDB instance not returned/discarded on tx timeout
> >>> • [TOMEE-2206] - Support for Enum injection in Microprofile JWT
> >>> New Feature
> >>> • [TOMEE-2209] - MicroProfile 1.2 Support
> >>> • [TOMEE-2210] - MicroProfile 1.3 Support
> >>> • [TOMEE-2211] - MicroProfile 1.2 Support - Configuration 1.1
> >>> • [TOMEE-2212] - MicroProfile 1.2 Support - Fault Tolerance 1.0
> >>> • [TOMEE-2213] - MicroProfile 1.2 Support - JWT Propagation 1.0
> >>> • [TOMEE-2214] - MicroProfile 1.2 Support - Health Check 1.0
> >>> • [TOMEE-2215] - MicroProfile 1.2 Support - Metrics 1.0
> >>> • [TOMEE-2216] - MicroProfile 1.3 Support - Config 1.2
> >>> • [TOMEE-2217] - MicroProfile 1.3 Support - Metrics 1.1
> >>> • [TOMEE-2218] - MicroProfile 1.3 Support - Rest Client 1.0
> >>> • [TOMEE-2219] - MicroProfile 1.3 Support - Open API 1.0
> >>> Improvement
> >>> • [TOMEE-2195] - Compile Error in
> >> /src/main/java/org/apache/openejb/config/AnnotationDeployer
> >>> • [TOMEE-2196] - keyStoreFile Property is Empty in Embedded
> >> Container
> >>> • [TOMEE-2221] - Use a Jsonb aware JAX-RS Provider
> >>> • [TOMEE-2222] - Enable create-tables for EclipseLink in Moviefun
> >> example
> >>> • [TOMEE-2224] - update to apache-parent-21 for sha512
> >>> Task
> >>> • [TOMEE-2159] - TomEE8: JSF 2.3
> >>> • [TOMEE-2160] - TomEE8: Servlet 4.0
> >>> • [TOMEE-2174] - Nested parameters prevent EJB interceptor
> matching
> >>> Dependency upgrade
> >>> • [TOMEE-2171] - Upgrade to ActiveMQ 5.15.3
> >>> • [TOMEE-2178] - TomEE8: Update to MyFaces 2.3.0 release
> >>> • [TOMEE-2179] - tomcat 9.0.8
> >>> • [TOMEE-2180] - johnzon 1.1.7
> >>> • [TOMEE-2184] - MyFaces 2.3.1
> >>> • [TOMEE-2186] - Upgrade CXF to 3.2.4
> >>> • [TOMEE-2187] - Upgrade to XBean 4.9
> >>> • [TOMEE-2207] - Update Bouncy Castle to 1.60
> >>>
> >>> Additionally, we have the following issue list associated to TomEE 8,
> >> that we need to update or decide if we need to do something with them
> for
> >> this release:
> >>> • [TOMEE-2115] - TomEE-8 work
> >>> • [TOMEE-2116] - Create javaee-api-8.0.0
> >>> • [TOMEE-2117] - Rework ProcessObserverMethod integration
> >>> • [TOMEE-2139] -
> >> org.apache.tomee.jul.handler.rotating.ArchivingTest broken in 2nd
> iteration
> >>> • [TOMEE-2140] - retire or fix arquillian-jpa example
> >>> • [TOMEE-2169] - Interceptor Bean injection does not work for EJBs
> >>> • [TOMEE-2185] - Add MP-JWT support
> >>> • [TOMEE-2227] - upgrade CXF to 3.2.6 and tomcat to 9.0.11
> >>> • [TOMEE-2197] - openejb.xml <Deployments jar="..."/> does not
> work
> >>>
> >>> Also, I guess that a lot of work was done without creating issues, so
> >> everything that was done is not completely reflected in this list. We
> may
> >> need to create some issues for that.
> >>>
> >>> Thanks!
> >>>
> >>> Cheers,
> >>> Roberto
> >>>
> >>>
> >>
> >>
>
>
Re: TomEE 8 Release Notes Preview
Posted by David Blevins <da...@gmail.com>.
Speaking from my own perspective, if we could get 11 support into the TomEE 8 release and *still* make the CodeOne date, that'd be amazing.
What is the best way for people to help?
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Sep 25, 2018, at 2:13 PM, Jonathan Gallimore <jo...@gmail.com> wrote:
>
> Question - we've merged some patches for Java 11, and to my knowledge
> libraries we use are ok with Java 11 (although I haven't personally worked
> through anything like all the testing I'd want to do). At the every least
> there are some jars we'd need to include in the distro for Java 11 - JAXB,
> Corba, RMI. Currently I'm trying to get 8.0.0 to _build_ with Java 11. Are
> we looking to push 8.0.0 out as is, or would we want to push the Java 11
> support and testing. Allowing a couple of weeks for votes, if we wanted to
> push Java 11 in 8.0.0 in the CodeOne timeframe, I could use some help.
>
> Jon
>
> On Tue, Sep 25, 2018 at 9:13 PM David Blevins <da...@gmail.com>
> wrote:
>
>> Hey Community!
>>
>> CodeOne (formerly JavaOne) is coming up at the end of October 22-25.
>> We've been wanting to get TomEE 8 out anyway, but getting something out a
>> week before code one would be an excellent opportunity to make some extra
>> noise. Knowing us, that'd mean we'd need to start actually rolling and
>> voting on releases pretty soon.
>>
>> Roberto, I know you were heavy on TomEE 8 release at one point. Where did
>> things leave off and are there any items people can help with?
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>>> On Aug 28, 2018, at 9:02 AM, Roberto Cortez <ra...@yahoo.com.INVALID>
>> wrote:
>>>
>>> Hi,
>>>
>>> I’m trying to compile a list of things regarding the TomEE 8 Release.
>> Right now, this is our preview for the Release Notes from JIRA:
>>>
>>> Bug
>>> • [TOMEE-2138] - MockitoExtension.Bean must implement Prioritized
>>> • [TOMEE-2167] - add <trim/> support for beans.xml
>>> • [TOMEE-2168] - upgrade maven-bundle-plugin to more recent version
>>> • [TOMEE-2172] - MDB instance not returned/discarded on tx timeout
>>> • [TOMEE-2206] - Support for Enum injection in Microprofile JWT
>>> New Feature
>>> • [TOMEE-2209] - MicroProfile 1.2 Support
>>> • [TOMEE-2210] - MicroProfile 1.3 Support
>>> • [TOMEE-2211] - MicroProfile 1.2 Support - Configuration 1.1
>>> • [TOMEE-2212] - MicroProfile 1.2 Support - Fault Tolerance 1.0
>>> • [TOMEE-2213] - MicroProfile 1.2 Support - JWT Propagation 1.0
>>> • [TOMEE-2214] - MicroProfile 1.2 Support - Health Check 1.0
>>> • [TOMEE-2215] - MicroProfile 1.2 Support - Metrics 1.0
>>> • [TOMEE-2216] - MicroProfile 1.3 Support - Config 1.2
>>> • [TOMEE-2217] - MicroProfile 1.3 Support - Metrics 1.1
>>> • [TOMEE-2218] - MicroProfile 1.3 Support - Rest Client 1.0
>>> • [TOMEE-2219] - MicroProfile 1.3 Support - Open API 1.0
>>> Improvement
>>> • [TOMEE-2195] - Compile Error in
>> /src/main/java/org/apache/openejb/config/AnnotationDeployer
>>> • [TOMEE-2196] - keyStoreFile Property is Empty in Embedded
>> Container
>>> • [TOMEE-2221] - Use a Jsonb aware JAX-RS Provider
>>> • [TOMEE-2222] - Enable create-tables for EclipseLink in Moviefun
>> example
>>> • [TOMEE-2224] - update to apache-parent-21 for sha512
>>> Task
>>> • [TOMEE-2159] - TomEE8: JSF 2.3
>>> • [TOMEE-2160] - TomEE8: Servlet 4.0
>>> • [TOMEE-2174] - Nested parameters prevent EJB interceptor matching
>>> Dependency upgrade
>>> • [TOMEE-2171] - Upgrade to ActiveMQ 5.15.3
>>> • [TOMEE-2178] - TomEE8: Update to MyFaces 2.3.0 release
>>> • [TOMEE-2179] - tomcat 9.0.8
>>> • [TOMEE-2180] - johnzon 1.1.7
>>> • [TOMEE-2184] - MyFaces 2.3.1
>>> • [TOMEE-2186] - Upgrade CXF to 3.2.4
>>> • [TOMEE-2187] - Upgrade to XBean 4.9
>>> • [TOMEE-2207] - Update Bouncy Castle to 1.60
>>>
>>> Additionally, we have the following issue list associated to TomEE 8,
>> that we need to update or decide if we need to do something with them for
>> this release:
>>> • [TOMEE-2115] - TomEE-8 work
>>> • [TOMEE-2116] - Create javaee-api-8.0.0
>>> • [TOMEE-2117] - Rework ProcessObserverMethod integration
>>> • [TOMEE-2139] -
>> org.apache.tomee.jul.handler.rotating.ArchivingTest broken in 2nd iteration
>>> • [TOMEE-2140] - retire or fix arquillian-jpa example
>>> • [TOMEE-2169] - Interceptor Bean injection does not work for EJBs
>>> • [TOMEE-2185] - Add MP-JWT support
>>> • [TOMEE-2227] - upgrade CXF to 3.2.6 and tomcat to 9.0.11
>>> • [TOMEE-2197] - openejb.xml <Deployments jar="..."/> does not work
>>>
>>> Also, I guess that a lot of work was done without creating issues, so
>> everything that was done is not completely reflected in this list. We may
>> need to create some issues for that.
>>>
>>> Thanks!
>>>
>>> Cheers,
>>> Roberto
>>>
>>>
>>
>>
Re: TomEE 8 Release Notes Preview
Posted by Jonathan Gallimore <jo...@gmail.com>.
Question - we've merged some patches for Java 11, and to my knowledge
libraries we use are ok with Java 11 (although I haven't personally worked
through anything like all the testing I'd want to do). At the every least
there are some jars we'd need to include in the distro for Java 11 - JAXB,
Corba, RMI. Currently I'm trying to get 8.0.0 to _build_ with Java 11. Are
we looking to push 8.0.0 out as is, or would we want to push the Java 11
support and testing. Allowing a couple of weeks for votes, if we wanted to
push Java 11 in 8.0.0 in the CodeOne timeframe, I could use some help.
Jon
On Tue, Sep 25, 2018 at 9:13 PM David Blevins <da...@gmail.com>
wrote:
> Hey Community!
>
> CodeOne (formerly JavaOne) is coming up at the end of October 22-25.
> We've been wanting to get TomEE 8 out anyway, but getting something out a
> week before code one would be an excellent opportunity to make some extra
> noise. Knowing us, that'd mean we'd need to start actually rolling and
> voting on releases pretty soon.
>
> Roberto, I know you were heavy on TomEE 8 release at one point. Where did
> things leave off and are there any items people can help with?
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Aug 28, 2018, at 9:02 AM, Roberto Cortez <ra...@yahoo.com.INVALID>
> wrote:
> >
> > Hi,
> >
> > I’m trying to compile a list of things regarding the TomEE 8 Release.
> Right now, this is our preview for the Release Notes from JIRA:
> >
> > Bug
> > • [TOMEE-2138] - MockitoExtension.Bean must implement Prioritized
> > • [TOMEE-2167] - add <trim/> support for beans.xml
> > • [TOMEE-2168] - upgrade maven-bundle-plugin to more recent version
> > • [TOMEE-2172] - MDB instance not returned/discarded on tx timeout
> > • [TOMEE-2206] - Support for Enum injection in Microprofile JWT
> > New Feature
> > • [TOMEE-2209] - MicroProfile 1.2 Support
> > • [TOMEE-2210] - MicroProfile 1.3 Support
> > • [TOMEE-2211] - MicroProfile 1.2 Support - Configuration 1.1
> > • [TOMEE-2212] - MicroProfile 1.2 Support - Fault Tolerance 1.0
> > • [TOMEE-2213] - MicroProfile 1.2 Support - JWT Propagation 1.0
> > • [TOMEE-2214] - MicroProfile 1.2 Support - Health Check 1.0
> > • [TOMEE-2215] - MicroProfile 1.2 Support - Metrics 1.0
> > • [TOMEE-2216] - MicroProfile 1.3 Support - Config 1.2
> > • [TOMEE-2217] - MicroProfile 1.3 Support - Metrics 1.1
> > • [TOMEE-2218] - MicroProfile 1.3 Support - Rest Client 1.0
> > • [TOMEE-2219] - MicroProfile 1.3 Support - Open API 1.0
> > Improvement
> > • [TOMEE-2195] - Compile Error in
> /src/main/java/org/apache/openejb/config/AnnotationDeployer
> > • [TOMEE-2196] - keyStoreFile Property is Empty in Embedded
> Container
> > • [TOMEE-2221] - Use a Jsonb aware JAX-RS Provider
> > • [TOMEE-2222] - Enable create-tables for EclipseLink in Moviefun
> example
> > • [TOMEE-2224] - update to apache-parent-21 for sha512
> > Task
> > • [TOMEE-2159] - TomEE8: JSF 2.3
> > • [TOMEE-2160] - TomEE8: Servlet 4.0
> > • [TOMEE-2174] - Nested parameters prevent EJB interceptor matching
> > Dependency upgrade
> > • [TOMEE-2171] - Upgrade to ActiveMQ 5.15.3
> > • [TOMEE-2178] - TomEE8: Update to MyFaces 2.3.0 release
> > • [TOMEE-2179] - tomcat 9.0.8
> > • [TOMEE-2180] - johnzon 1.1.7
> > • [TOMEE-2184] - MyFaces 2.3.1
> > • [TOMEE-2186] - Upgrade CXF to 3.2.4
> > • [TOMEE-2187] - Upgrade to XBean 4.9
> > • [TOMEE-2207] - Update Bouncy Castle to 1.60
> >
> > Additionally, we have the following issue list associated to TomEE 8,
> that we need to update or decide if we need to do something with them for
> this release:
> > • [TOMEE-2115] - TomEE-8 work
> > • [TOMEE-2116] - Create javaee-api-8.0.0
> > • [TOMEE-2117] - Rework ProcessObserverMethod integration
> > • [TOMEE-2139] -
> org.apache.tomee.jul.handler.rotating.ArchivingTest broken in 2nd iteration
> > • [TOMEE-2140] - retire or fix arquillian-jpa example
> > • [TOMEE-2169] - Interceptor Bean injection does not work for EJBs
> > • [TOMEE-2185] - Add MP-JWT support
> > • [TOMEE-2227] - upgrade CXF to 3.2.6 and tomcat to 9.0.11
> > • [TOMEE-2197] - openejb.xml <Deployments jar="..."/> does not work
> >
> > Also, I guess that a lot of work was done without creating issues, so
> everything that was done is not completely reflected in this list. We may
> need to create some issues for that.
> >
> > Thanks!
> >
> > Cheers,
> > Roberto
> >
> >
>
>