Re: TomEE-7.0.5 work

2018-06-17 Thread Mark Struberg 
Just looked what we do in fb_tomee8. And found the following:

@Ignore //X TODO see TOMEE-2139 currently broken due to #f24c42e2212c575
We cannot release with this test. 

LieGrue,
strub


> Am 17.06.2018 um 14:03 schrieb Romain Manni-Bucau :
> 
> Can need a clean to pass IIRC. Code is unrelated to tomcat actually
> 
> Le dim. 17 juin 2018 12:16, Mark Struberg  a
> écrit :
> 
>> That rotating test seems to stick.
>> 
>> Might have to do with a minor tomcat behaviour change.
>> Something which is at least not behaving stochastic and we can work on it.
>> Will try to tackle it tonight.
>> 
>> LieGrue,
>> strub
>> 
>>> Am 17.06.2018 um 11:50 schrieb Mark Struberg >> :
>>> 
>>> That's the goal :D
>>> 
>>> I will be offline this afternoon, just like to providing feedback and
>> pick up in the evening again.
>>> Those are all stochastic failures. Once you resume from there they will
>> likely work fine again :(
>>> Of course that's frustrating to a potential new committer, so we should
>> rather solve those failures.
>>> 
>>> Next one: :)
>>> 
>>> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 24.382 s <<< FAILURE! - in
>> org.apache.tomee.jul.handler.rotating.ArchivingTest
>>> [ERROR]
>> logAndRotateAndPurge[gzip](org.apache.tomee.jul.handler.rotating.ArchivingTest)
>> Time elapsed: 5.425 s  <<< FAILURE!
>>> java.lang.AssertionError
>>>  at org.junit.Assert.fail(Assert.java:86)
>>>  at org.junit.Assert.assertTrue(Assert.java:41)
>>>  at org.junit.Assert.assertTrue(Assert.java:52)
>>>  at
>> org.apache.tomee.jul.handler.rotating.ArchivingTest.logAndRotateAndPurge(ArchivingTest.java:207)
>>> 
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
 Am 17.06.2018 um 11:46 schrieb Jonathan Gallimore <
>> jonathan.gallim...@gmail.com>:
 
 I'll take a look - I think my last build was green. If we sort these
>> out,
 are we good to release? I'm happy to do the actual release.
 
 Jon
 
 On Sun, 17 Jun 2018, 10:37 Mark Struberg, 
>> wrote:
 
> And another one which seems regularly failing since 2 years:
> 
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 38.736 s <<< FAILURE! - in
>> org.apache.openejb.itest.legacy.LegacyServerTest
> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
> elapsed: 38.661 s  <<< FAILURE!
> java.lang.AssertionError: Bad number of invocations for the bean
>> "green".
> expected:<2> but was:<1>
>  at org.junit.Assert.fail(Assert.java:88)
>  at org.junit.Assert.failNotEquals(Assert.java:834)
>  at org.junit.Assert.assertEquals(Assert.java:645)
>  at
> 
>> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
> 
> 
> It's really hard to do a realease that way.
> Is the logic of the test itself broken or is it really a problem in our
> impl? Afaict it's the former. So probably remove the test?
> 
> LieGrue,
> strub
> 
> 
>> Am 17.06.2018 um 11:04 schrieb Mark Struberg
>> > :
>> 
>> OpenJPA updated to 2.4.3.
>> 
>> But still getting random test errors.
>> 
>> Failed tests:
>> ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
>> 
>> 
>> 
> 
>> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
> Time elapsed: 0.836 sec  <<< FAILURE!
>> java.lang.AssertionError
>> at org.junit.Assert.fail(Assert.java:86)
>> at org.junit.Assert.assertTrue(Assert.java:41)
>> at org.junit.Assert.assertTrue(Assert.java:52)
>> at
> 
>> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
>> 
>> 
>> LieGrue,
>> strub
>> 
>> 
>> 
>>> Am 07.06.2018 um 00:08 schrieb Mark Struberg
>> > :
>>> 
>>> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
>>> 
>>> LieGrue,
>>> strub
>>> 
 Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
 
 I think we're still looking for an OpenJPA release (unless I missed
> it).
 
 Jon
 
 On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
> wrote:
 
> Hello,
> 
> I TomEE 7.0.5 finally ready to be released?
> (I don't see new activity for 1 month on this intention to release,
> what's blocking?)
> 
> Best regards,
> Alexandre
> 
> 
> 2018-05-05 10:53 GMT+02:00 Mark Struberg >> :
>> btw, link to the buildbot is here
>> https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 05.05.2018 um 10:49 schrieb Mark Struberg
> > :
>>> 
>>>

Re: TomEE-7.0.5 work

2018-06-17 Thread Romain Manni-Bucau 
Can need a clean to pass IIRC. Code is unrelated to tomcat actually

Le dim. 17 juin 2018 12:16, Mark Struberg  a
écrit :

> That rotating test seems to stick.
>
> Might have to do with a minor tomcat behaviour change.
> Something which is at least not behaving stochastic and we can work on it.
> Will try to tackle it tonight.
>
> LieGrue,
> strub
>
> > Am 17.06.2018 um 11:50 schrieb Mark Struberg  >:
> >
> > That's the goal :D
> >
> > I will be offline this afternoon, just like to providing feedback and
> pick up in the evening again.
> > Those are all stochastic failures. Once you resume from there they will
> likely work fine again :(
> > Of course that's frustrating to a potential new committer, so we should
> rather solve those failures.
> >
> > Next one: :)
> >
> > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 24.382 s <<< FAILURE! - in
> org.apache.tomee.jul.handler.rotating.ArchivingTest
> > [ERROR]
> logAndRotateAndPurge[gzip](org.apache.tomee.jul.handler.rotating.ArchivingTest)
> Time elapsed: 5.425 s  <<< FAILURE!
> > java.lang.AssertionError
> >   at org.junit.Assert.fail(Assert.java:86)
> >   at org.junit.Assert.assertTrue(Assert.java:41)
> >   at org.junit.Assert.assertTrue(Assert.java:52)
> >   at
> org.apache.tomee.jul.handler.rotating.ArchivingTest.logAndRotateAndPurge(ArchivingTest.java:207)
> >
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 17.06.2018 um 11:46 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >>
> >> I'll take a look - I think my last build was green. If we sort these
> out,
> >> are we good to release? I'm happy to do the actual release.
> >>
> >> Jon
> >>
> >> On Sun, 17 Jun 2018, 10:37 Mark Struberg, 
> wrote:
> >>
> >>> And another one which seems regularly failing since 2 years:
> >>>
> >>> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> >>> 38.736 s <<< FAILURE! - in
> org.apache.openejb.itest.legacy.LegacyServerTest
> >>> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
> >>> elapsed: 38.661 s  <<< FAILURE!
> >>> java.lang.AssertionError: Bad number of invocations for the bean
> "green".
> >>> expected:<2> but was:<1>
> >>>   at org.junit.Assert.fail(Assert.java:88)
> >>>   at org.junit.Assert.failNotEquals(Assert.java:834)
> >>>   at org.junit.Assert.assertEquals(Assert.java:645)
> >>>   at
> >>>
> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
> >>>
> >>>
> >>> It's really hard to do a realease that way.
> >>> Is the logic of the test itself broken or is it really a problem in our
> >>> impl? Afaict it's the former. So probably remove the test?
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
>  Am 17.06.2018 um 11:04 schrieb Mark Struberg
>   :
> 
>  OpenJPA updated to 2.4.3.
> 
>  But still getting random test errors.
> 
>  Failed tests:
>  ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
> 
> 
> 
> >>>
> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
> >>> Time elapsed: 0.836 sec  <<< FAILURE!
>  java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at
> >>>
> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
> 
> 
>  LieGrue,
>  strub
> 
> 
> 
> > Am 07.06.2018 um 00:08 schrieb Mark Struberg
>   :
> >
> > Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> >
> > LieGrue,
> > strub
> >
> >> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
> >>> jonathan.gallim...@gmail.com>:
> >>
> >> I think we're still looking for an OpenJPA release (unless I missed
> >>> it).
> >>
> >> Jon
> >>
> >> On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
> >>> wrote:
> >>
> >>> Hello,
> >>>
> >>> I TomEE 7.0.5 finally ready to be released?
> >>> (I don't see new activity for 1 month on this intention to release,
> >>> what's blocking?)
> >>>
> >>> Best regards,
> >>> Alexandre
> >>>
> >>>
> >>> 2018-05-05 10:53 GMT+02:00 Mark Struberg  >:
>  btw, link to the buildbot is here
>  https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
> 
>  LieGrue,
>  strub
> 
> 
> > Am 05.05.2018 um 10:49 schrieb Mark Struberg
> >>>   :
> >
> > master build is broken since a while!
> >
> > [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-surefire-plugin:2.20:test
> >>> (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
> >>> There are
> >>> test failures.
> > [ERROR]
> >
> >
>

Re: TomEE-7.0.5 work

2018-06-17 Thread Mark Struberg 
That rotating test seems to stick. 

Might have to do with a minor tomcat behaviour change.
Something which is at least not behaving stochastic and we can work on it.
Will try to tackle it tonight.

LieGrue,
strub

> Am 17.06.2018 um 11:50 schrieb Mark Struberg :
> 
> That's the goal :D
> 
> I will be offline this afternoon, just like to providing feedback and pick up 
> in the evening again.
> Those are all stochastic failures. Once you resume from there they will 
> likely work fine again :(
> Of course that's frustrating to a potential new committer, so we should 
> rather solve those failures.
> 
> Next one: :)
> 
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.382 s <<< FAILURE! - in org.apache.tomee.jul.handler.rotating.ArchivingTest
> [ERROR] 
> logAndRotateAndPurge[gzip](org.apache.tomee.jul.handler.rotating.ArchivingTest)
>   Time elapsed: 5.425 s  <<< FAILURE!
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.tomee.jul.handler.rotating.ArchivingTest.logAndRotateAndPurge(ArchivingTest.java:207)
> 
> 
> LieGrue,
> strub
> 
> 
>> Am 17.06.2018 um 11:46 schrieb Jonathan Gallimore 
>> :
>> 
>> I'll take a look - I think my last build was green. If we sort these out,
>> are we good to release? I'm happy to do the actual release.
>> 
>> Jon
>> 
>> On Sun, 17 Jun 2018, 10:37 Mark Struberg,  wrote:
>> 
>>> And another one which seems regularly failing since 2 years:
>>> 
>>> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>>> 38.736 s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
>>> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
>>> elapsed: 38.661 s  <<< FAILURE!
>>> java.lang.AssertionError: Bad number of invocations for the bean "green".
>>> expected:<2> but was:<1>
>>>   at org.junit.Assert.fail(Assert.java:88)
>>>   at org.junit.Assert.failNotEquals(Assert.java:834)
>>>   at org.junit.Assert.assertEquals(Assert.java:645)
>>>   at
>>> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
>>> 
>>> 
>>> It's really hard to do a realease that way.
>>> Is the logic of the test itself broken or is it really a problem in our
>>> impl? Afaict it's the former. So probably remove the test?
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
 Am 17.06.2018 um 11:04 schrieb Mark Struberg >>> :
 
 OpenJPA updated to 2.4.3.
 
 But still getting random test errors.
 
 Failed tests:
 ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
 
 
 
>>> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
>>> Time elapsed: 0.836 sec  <<< FAILURE!
 java.lang.AssertionError
  at org.junit.Assert.fail(Assert.java:86)
  at org.junit.Assert.assertTrue(Assert.java:41)
  at org.junit.Assert.assertTrue(Assert.java:52)
  at
>>> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
 
 
 LieGrue,
 strub
 
 
 
> Am 07.06.2018 um 00:08 schrieb Mark Struberg >>> :
> 
> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> 
> LieGrue,
> strub
> 
>> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
>>> jonathan.gallim...@gmail.com>:
>> 
>> I think we're still looking for an OpenJPA release (unless I missed
>>> it).
>> 
>> Jon
>> 
>> On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
>>> wrote:
>> 
>>> Hello,
>>> 
>>> I TomEE 7.0.5 finally ready to be released?
>>> (I don't see new activity for 1 month on this intention to release,
>>> what's blocking?)
>>> 
>>> Best regards,
>>> Alexandre
>>> 
>>> 
>>> 2018-05-05 10:53 GMT+02:00 Mark Struberg :
 btw, link to the buildbot is here
 https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
 
 LieGrue,
 strub
 
 
> Am 05.05.2018 um 10:49 schrieb Mark Struberg
>>> >>> :
> 
> master build is broken since a while!
> 
> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.20:test
>>> (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
>>> There are
>>> test failures.
> [ERROR]
> 
> 
> The rest seems to work fine.
> So I gonna push forward with the Johnzon-1.0.1 release
> 
> Can anybody have a look at it?
> 
> txs and LieGrue,
> strub
> 
> 
> 
>> Am 04.05.2018 um 22:05 schrieb Mark Struberg
>>> >>> :
>> 
>> I've now also deployed fresh snapshots and will update in master

Re: TomEE-7.0.5 work

2018-06-17 Thread Jonathan Gallimore 
I also won't be around until the evening, but happy to check it out and
kick off the release if we're looking good.

Jon

On Sun, 17 Jun 2018, 10:51 Mark Struberg,  wrote:

> That's the goal :D
>
> I will be offline this afternoon, just like to providing feedback and pick
> up in the evening again.
> Those are all stochastic failures. Once you resume from there they will
> likely work fine again :(
> Of course that's frustrating to a potential new committer, so we should
> rather solve those failures.
>
> Next one: :)
>
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 24.382 s <<< FAILURE! - in
> org.apache.tomee.jul.handler.rotating.ArchivingTest
> [ERROR]
> logAndRotateAndPurge[gzip](org.apache.tomee.jul.handler.rotating.ArchivingTest)
> Time elapsed: 5.425 s  <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.tomee.jul.handler.rotating.ArchivingTest.logAndRotateAndPurge(ArchivingTest.java:207)
>
>
> LieGrue,
> strub
>
>
> > Am 17.06.2018 um 11:46 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >
> > I'll take a look - I think my last build was green. If we sort these out,
> > are we good to release? I'm happy to do the actual release.
> >
> > Jon
> >
> > On Sun, 17 Jun 2018, 10:37 Mark Struberg, 
> wrote:
> >
> >> And another one which seems regularly failing since 2 years:
> >>
> >> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> >> 38.736 s <<< FAILURE! - in
> org.apache.openejb.itest.legacy.LegacyServerTest
> >> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
> >> elapsed: 38.661 s  <<< FAILURE!
> >> java.lang.AssertionError: Bad number of invocations for the bean
> "green".
> >> expected:<2> but was:<1>
> >>at org.junit.Assert.fail(Assert.java:88)
> >>at org.junit.Assert.failNotEquals(Assert.java:834)
> >>at org.junit.Assert.assertEquals(Assert.java:645)
> >>at
> >>
> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
> >>
> >>
> >> It's really hard to do a realease that way.
> >> Is the logic of the test itself broken or is it really a problem in our
> >> impl? Afaict it's the former. So probably remove the test?
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 17.06.2018 um 11:04 schrieb Mark Struberg  >>> :
> >>>
> >>> OpenJPA updated to 2.4.3.
> >>>
> >>> But still getting random test errors.
> >>>
> >>> Failed tests:
> >>> ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
> >>>
> >>>
> >>>
> >>
> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
> >> Time elapsed: 0.836 sec  <<< FAILURE!
> >>> java.lang.AssertionError
> >>>   at org.junit.Assert.fail(Assert.java:86)
> >>>   at org.junit.Assert.assertTrue(Assert.java:41)
> >>>   at org.junit.Assert.assertTrue(Assert.java:52)
> >>>   at
> >>
> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
> >>>
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>>
>  Am 07.06.2018 um 00:08 schrieb Mark Struberg
>  >>> :
> 
>  Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> 
>  LieGrue,
>  strub
> 
> > Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
> >> jonathan.gallim...@gmail.com>:
> >
> > I think we're still looking for an OpenJPA release (unless I missed
> >> it).
> >
> > Jon
> >
> > On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
> >> wrote:
> >
> >> Hello,
> >>
> >> I TomEE 7.0.5 finally ready to be released?
> >> (I don't see new activity for 1 month on this intention to release,
> >> what's blocking?)
> >>
> >> Best regards,
> >> Alexandre
> >>
> >>
> >> 2018-05-05 10:53 GMT+02:00 Mark Struberg  >:
> >>> btw, link to the buildbot is here
> >>> https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
>  Am 05.05.2018 um 10:49 schrieb Mark Struberg
> >>  >>> :
> 
>  master build is broken since a while!
> 
>  [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-surefire-plugin:2.20:test
> >> (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
> >> There are
> >> test failures.
>  [ERROR]
> 
> 
>  The rest seems to work fine.
>  So I gonna push forward with the Johnzon-1.0.1 release
> 
>  Can anybody have a look at it?
> 
>  txs and LieGrue,
>  strub
> 
> 
> 
> > Am 04.05.2018 um 22:05 schrieb Mark Struberg
> >>  >>> :
> >
> > I've now also deployed fresh

Re: TomEE-7.0.5 work

2018-06-17 Thread Mark Struberg 
That's the goal :D

I will be offline this afternoon, just like to providing feedback and pick up 
in the evening again.
Those are all stochastic failures. Once you resume from there they will likely 
work fine again :(
Of course that's frustrating to a potential new committer, so we should rather 
solve those failures.

Next one: :)

[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 24.382 
s <<< FAILURE! - in org.apache.tomee.jul.handler.rotating.ArchivingTest
[ERROR] 
logAndRotateAndPurge[gzip](org.apache.tomee.jul.handler.rotating.ArchivingTest) 
 Time elapsed: 5.425 s  <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.tomee.jul.handler.rotating.ArchivingTest.logAndRotateAndPurge(ArchivingTest.java:207)


LieGrue,
strub


> Am 17.06.2018 um 11:46 schrieb Jonathan Gallimore 
> :
> 
> I'll take a look - I think my last build was green. If we sort these out,
> are we good to release? I'm happy to do the actual release.
> 
> Jon
> 
> On Sun, 17 Jun 2018, 10:37 Mark Struberg,  wrote:
> 
>> And another one which seems regularly failing since 2 years:
>> 
>> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 38.736 s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
>> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
>> elapsed: 38.661 s  <<< FAILURE!
>> java.lang.AssertionError: Bad number of invocations for the bean "green".
>> expected:<2> but was:<1>
>>at org.junit.Assert.fail(Assert.java:88)
>>at org.junit.Assert.failNotEquals(Assert.java:834)
>>at org.junit.Assert.assertEquals(Assert.java:645)
>>at
>> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
>> 
>> 
>> It's really hard to do a realease that way.
>> Is the logic of the test itself broken or is it really a problem in our
>> impl? Afaict it's the former. So probably remove the test?
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 17.06.2018 um 11:04 schrieb Mark Struberg >> :
>>> 
>>> OpenJPA updated to 2.4.3.
>>> 
>>> But still getting random test errors.
>>> 
>>> Failed tests:
>>> ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
>>> 
>>> 
>>> 
>> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
>> Time elapsed: 0.836 sec  <<< FAILURE!
>>> java.lang.AssertionError
>>>   at org.junit.Assert.fail(Assert.java:86)
>>>   at org.junit.Assert.assertTrue(Assert.java:41)
>>>   at org.junit.Assert.assertTrue(Assert.java:52)
>>>   at
>> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
>>> 
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
>>> 
 Am 07.06.2018 um 00:08 schrieb Mark Struberg >> :
 
 Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
 
 LieGrue,
 strub
 
> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
>> jonathan.gallim...@gmail.com>:
> 
> I think we're still looking for an OpenJPA release (unless I missed
>> it).
> 
> Jon
> 
> On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
>> wrote:
> 
>> Hello,
>> 
>> I TomEE 7.0.5 finally ready to be released?
>> (I don't see new activity for 1 month on this intention to release,
>> what's blocking?)
>> 
>> Best regards,
>> Alexandre
>> 
>> 
>> 2018-05-05 10:53 GMT+02:00 Mark Struberg :
>>> btw, link to the buildbot is here
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
 Am 05.05.2018 um 10:49 schrieb Mark Struberg
>> >> :
 
 master build is broken since a while!
 
 [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.20:test
>> (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
>> There are
>> test failures.
 [ERROR]
 
 
 The rest seems to work fine.
 So I gonna push forward with the Johnzon-1.0.1 release
 
 Can anybody have a look at it?
 
 txs and LieGrue,
 strub
 
 
 
> Am 04.05.2018 um 22:05 schrieb Mark Struberg
>> >> :
> 
> I've now also deployed fresh snapshots and will update in master
> 
> LieGrue,
> strub
> 
> 
>> Am 04.05.2018 um 21:53 schrieb Mark Struberg
>> :
>> 
>> Yes, working on it.
>> 
>> But I only see 2 bugs reported for this release.
>> 
>> https://issues.apache.org/jira/projects/JOHNZON/versions/12340497
>> 
>> 
>> JOHNZON-160 org.apache.johnzon.mapper.MapperException:
>>

Re: TomEE-7.0.5 work

2018-06-17 Thread Romain Manni-Bucau 
A computer issue due to the need of a time related test?
The lastest can be a network issue on mac (already saw) or defaulting of
our net interface selection.

Le dim. 17 juin 2018 11:37, Mark Struberg  a
écrit :

> And another one which seems regularly failing since 2 years:
>
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 38.736 s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
> elapsed: 38.661 s  <<< FAILURE!
> java.lang.AssertionError: Bad number of invocations for the bean "green".
> expected:<2> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
>
>
> It's really hard to do a realease that way.
> Is the logic of the test itself broken or is it really a problem in our
> impl? Afaict it's the former. So probably remove the test?
>
> LieGrue,
> strub
>
>
> > Am 17.06.2018 um 11:04 schrieb Mark Struberg  >:
> >
> > OpenJPA updated to 2.4.3.
> >
> > But still getting random test errors.
> >
> > Failed tests:
> >  ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
> >
> >
> >
> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
> Time elapsed: 0.836 sec  <<< FAILURE!
> > java.lang.AssertionError
> >at org.junit.Assert.fail(Assert.java:86)
> >at org.junit.Assert.assertTrue(Assert.java:41)
> >at org.junit.Assert.assertTrue(Assert.java:52)
> >at
> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >> Am 07.06.2018 um 00:08 schrieb Mark Struberg  >:
> >>
> >> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> >>
> >> LieGrue,
> >> strub
> >>
> >>> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >>>
> >>> I think we're still looking for an OpenJPA release (unless I missed
> it).
> >>>
> >>> Jon
> >>>
> >>> On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
> wrote:
> >>>
>  Hello,
> 
>  I TomEE 7.0.5 finally ready to be released?
>  (I don't see new activity for 1 month on this intention to release,
>  what's blocking?)
> 
>  Best regards,
>  Alexandre
> 
> 
>  2018-05-05 10:53 GMT+02:00 Mark Struberg :
> > btw, link to the buildbot is here
> > https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 05.05.2018 um 10:49 schrieb Mark Struberg
>  > :
> >>
> >> master build is broken since a while!
> >>
> >> [ERROR] Failed to execute goal
>  org.apache.maven.plugins:maven-surefire-plugin:2.20:test
>  (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
> There are
>  test failures.
> >> [ERROR]
> >>
> >>
> >> The rest seems to work fine.
> >> So I gonna push forward with the Johnzon-1.0.1 release
> >>
> >> Can anybody have a look at it?
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >>
> >>> Am 04.05.2018 um 22:05 schrieb Mark Struberg
>  > :
> >>>
> >>> I've now also deployed fresh snapshots and will update in master
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
>  Am 04.05.2018 um 21:53 schrieb Mark Struberg
>  :
> 
>  Yes, working on it.
> 
>  But I only see 2 bugs reported for this release.
> 
>  https://issues.apache.org/jira/projects/JOHNZON/versions/12340497
> 
> 
>  JOHNZON-160 org.apache.johnzon.mapper.MapperException:
>  ObjectConverters are only supported for Classes not Types
> Unassigned
>  Resolved
>  JOHNZON-101 JsonObject#getJson* must not throw
> NullPointerException
>  Reinhard Sandtner   Closed
> 
> 
>  I now applied the patch - thanks again to Jon for doing all  the
> work!
> 
>  I've also went through the changes (hack, that was a lot!) and
> tried
>  to extract the ticket numbers:
> 
> 
> https://issues.apache.org/jira/projects/JOHNZON/versions/12340497#release-report-tab-body
> 
>  So I'm ready to roll the Johnzon-1.0.1 release ^^
> 
>  Will keep you updated.
> 
>  LieGrue,
>  strub
> 
> > Am 02.05.2018 um 22:45 schrieb Alex The Rocker <
> alex.m3...@gmail.com
> > :
> >
> > Hello,
> >
> > Now that OWB-1.7.5 vote passed, how about Johnzon 1.0.1 for
> upcoming
> > TomEE 7.0.5?
> > Shouldn't there be a vote to officialize Johnzon 1.0.1?
> >
>

Re: TomEE-7.0.5 work

2018-06-17 Thread Jonathan Gallimore 
I'll take a look - I think my last build was green. If we sort these out,
are we good to release? I'm happy to do the actual release.

Jon

On Sun, 17 Jun 2018, 10:37 Mark Struberg,  wrote:

> And another one which seems regularly failing since 2 years:
>
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 38.736 s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
> [ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time
> elapsed: 38.661 s  <<< FAILURE!
> java.lang.AssertionError: Bad number of invocations for the bean "green".
> expected:<2> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)
>
>
> It's really hard to do a realease that way.
> Is the logic of the test itself broken or is it really a problem in our
> impl? Afaict it's the former. So probably remove the test?
>
> LieGrue,
> strub
>
>
> > Am 17.06.2018 um 11:04 schrieb Mark Struberg  >:
> >
> > OpenJPA updated to 2.4.3.
> >
> > But still getting random test errors.
> >
> > Failed tests:
> >  ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
> >
> >
> >
> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
> Time elapsed: 0.836 sec  <<< FAILURE!
> > java.lang.AssertionError
> >at org.junit.Assert.fail(Assert.java:86)
> >at org.junit.Assert.assertTrue(Assert.java:41)
> >at org.junit.Assert.assertTrue(Assert.java:52)
> >at
> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >> Am 07.06.2018 um 00:08 schrieb Mark Struberg  >:
> >>
> >> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> >>
> >> LieGrue,
> >> strub
> >>
> >>> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >>>
> >>> I think we're still looking for an OpenJPA release (unless I missed
> it).
> >>>
> >>> Jon
> >>>
> >>> On Tue, 5 Jun 2018, 14:03 Alex The Rocker, 
> wrote:
> >>>
>  Hello,
> 
>  I TomEE 7.0.5 finally ready to be released?
>  (I don't see new activity for 1 month on this intention to release,
>  what's blocking?)
> 
>  Best regards,
>  Alexandre
> 
> 
>  2018-05-05 10:53 GMT+02:00 Mark Struberg :
> > btw, link to the buildbot is here
> > https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 05.05.2018 um 10:49 schrieb Mark Struberg
>  > :
> >>
> >> master build is broken since a while!
> >>
> >> [ERROR] Failed to execute goal
>  org.apache.maven.plugins:maven-surefire-plugin:2.20:test
>  (test-tomee-remote) on project arquillian-tomee-webprofile-tests:
> There are
>  test failures.
> >> [ERROR]
> >>
> >>
> >> The rest seems to work fine.
> >> So I gonna push forward with the Johnzon-1.0.1 release
> >>
> >> Can anybody have a look at it?
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >>
> >>> Am 04.05.2018 um 22:05 schrieb Mark Struberg
>  > :
> >>>
> >>> I've now also deployed fresh snapshots and will update in master
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
>  Am 04.05.2018 um 21:53 schrieb Mark Struberg
>  :
> 
>  Yes, working on it.
> 
>  But I only see 2 bugs reported for this release.
> 
>  https://issues.apache.org/jira/projects/JOHNZON/versions/12340497
> 
> 
>  JOHNZON-160 org.apache.johnzon.mapper.MapperException:
>  ObjectConverters are only supported for Classes not Types
> Unassigned
>  Resolved
>  JOHNZON-101 JsonObject#getJson* must not throw
> NullPointerException
>  Reinhard Sandtner   Closed
> 
> 
>  I now applied the patch - thanks again to Jon for doing all  the
> work!
> 
>  I've also went through the changes (hack, that was a lot!) and
> tried
>  to extract the ticket numbers:
> 
> 
> https://issues.apache.org/jira/projects/JOHNZON/versions/12340497#release-report-tab-body
> 
>  So I'm ready to roll the Johnzon-1.0.1 release ^^
> 
>  Will keep you updated.
> 
>  LieGrue,
>  strub
> 
> > Am 02.05.2018 um 22:45 schrieb Alex The Rocker <
> alex.m3...@gmail.com
> > :
> >
> > Hello,
> >
> > Now that OWB-1.7.5 vote passed, how about Johnzon 1.0.1 for
> upcoming
> > TomEE 7.0.5?
> > Shouldn't there be a vote to officialize Johnzon 1.0.1?
> >
> > Best

Re: TomEE-7.0.5 work

2018-06-17 Thread Mark Struberg 
And another one which seems regularly failing since 2 years:

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 38.736 
s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
[ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest)  Time elapsed: 
38.661 s  <<< FAILURE!
java.lang.AssertionError: Bad number of invocations for the bean "green". 
expected:<2> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at 
org.apache.openejb.itest.legacy.LegacyServerTest.assertBalance(LegacyServerTest.java:219)


It's really hard to do a realease that way. 
Is the logic of the test itself broken or is it really a problem in our impl? 
Afaict it's the former. So probably remove the test?

LieGrue,
strub


> Am 17.06.2018 um 11:04 schrieb Mark Struberg :
> 
> OpenJPA updated to 2.4.3.
> 
> But still getting random test errors.
> 
> Failed tests:
>  ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
> 
> 
> triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
>   Time elapsed: 0.836 sec  <<< FAILURE!
> java.lang.AssertionError
>at org.junit.Assert.fail(Assert.java:86)
>at org.junit.Assert.assertTrue(Assert.java:41)
>at org.junit.Assert.assertTrue(Assert.java:52)
>at 
> org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)
> 
> 
> LieGrue,
> strub
> 
> 
> 
>> Am 07.06.2018 um 00:08 schrieb Mark Struberg :
>> 
>> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
>> 
>> LieGrue,
>> strub
>> 
>>> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore 
>>> :
>>> 
>>> I think we're still looking for an OpenJPA release (unless I missed it).
>>> 
>>> Jon
>>> 
>>> On Tue, 5 Jun 2018, 14:03 Alex The Rocker,  wrote:
>>> 
 Hello,
 
 I TomEE 7.0.5 finally ready to be released?
 (I don't see new activity for 1 month on this intention to release,
 what's blocking?)
 
 Best regards,
 Alexandre
 
 
 2018-05-05 10:53 GMT+02:00 Mark Struberg :
> btw, link to the buildbot is here
> https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
> 
> LieGrue,
> strub
> 
> 
>> Am 05.05.2018 um 10:49 schrieb Mark Struberg  :
>> 
>> master build is broken since a while!
>> 
>> [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-surefire-plugin:2.20:test
 (test-tomee-remote) on project arquillian-tomee-webprofile-tests: There are
 test failures.
>> [ERROR]
>> 
>> 
>> The rest seems to work fine.
>> So I gonna push forward with the Johnzon-1.0.1 release
>> 
>> Can anybody have a look at it?
>> 
>> txs and LieGrue,
>> strub
>> 
>> 
>> 
>>> Am 04.05.2018 um 22:05 schrieb Mark Struberg  :
>>> 
>>> I've now also deployed fresh snapshots and will update in master
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
 Am 04.05.2018 um 21:53 schrieb Mark Struberg
 :
 
 Yes, working on it.
 
 But I only see 2 bugs reported for this release.
 
 https://issues.apache.org/jira/projects/JOHNZON/versions/12340497
 
 
 JOHNZON-160 org.apache.johnzon.mapper.MapperException:
 ObjectConverters are only supported for Classes not TypesUnassigned
 Resolved
 JOHNZON-101 JsonObject#getJson* must not throw NullPointerException
 Reinhard Sandtner   Closed
 
 
 I now applied the patch - thanks again to Jon for doing all  the work!
 
 I've also went through the changes (hack, that was a lot!) and tried
 to extract the ticket numbers:
 
 https://issues.apache.org/jira/projects/JOHNZON/versions/12340497#release-report-tab-body
 
 So I'm ready to roll the Johnzon-1.0.1 release ^^
 
 Will keep you updated.
 
 LieGrue,
 strub
 
> Am 02.05.2018 um 22:45 schrieb Alex The Rocker  :
> 
> Hello,
> 
> Now that OWB-1.7.5 vote passed, how about Johnzon 1.0.1 for upcoming
> TomEE 7.0.5?
> Shouldn't there be a vote to officialize Johnzon 1.0.1?
> 
> Best regards,
> Alexandre
> 
> 
> 2018-04-29 13:04 GMT+02:00 Mark Struberg  :
>> The OWB-1.7.5 vote is on the list now.
>> 
>> LieGrue,
>> strub
>> 
>>> Am 27.04.2018 um 15:16 schrieb Romain Manni-Bucau <
 rmannibu...@gmail.com>:
>>> 
>>> We are working with Mark on a release train soon, johnzon would be
 part of
>>> it probably.
>>> An OWB release is needed too AFAIK and is on its way.

Re: TomEE-7.0.5 work

2018-06-17 Thread Mark Struberg 
OpenJPA updated to 2.4.3.

But still getting random test errors.

Failed tests:
  ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null


triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
  Time elapsed: 0.836 sec  <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.openejb.threads.ManagedScheduledExecutorServiceTest.triggerRunnableSchedule(ManagedScheduledExecutorServiceTest.java:124)


LieGrue,
strub



> Am 07.06.2018 um 00:08 schrieb Mark Struberg :
> 
> Just started a vote for openjpa-2.4.3. And 3.0 will follow soon.
> 
> LieGrue,
> strub
> 
>> Am 05.06.2018 um 17:45 schrieb Jonathan Gallimore 
>> :
>> 
>> I think we're still looking for an OpenJPA release (unless I missed it).
>> 
>> Jon
>> 
>> On Tue, 5 Jun 2018, 14:03 Alex The Rocker,  wrote:
>> 
>>> Hello,
>>> 
>>> I TomEE 7.0.5 finally ready to be released?
>>> (I don't see new activity for 1 month on this intention to release,
>>> what's blocking?)
>>> 
>>> Best regards,
>>> Alexandre
>>> 
>>> 
>>> 2018-05-05 10:53 GMT+02:00 Mark Struberg :
 btw, link to the buildbot is here
 https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/920
 
 LieGrue,
 strub
 
 
> Am 05.05.2018 um 10:49 schrieb Mark Struberg >>> :
> 
> master build is broken since a while!
> 
> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.20:test
>>> (test-tomee-remote) on project arquillian-tomee-webprofile-tests: There are
>>> test failures.
> [ERROR]
> 
> 
> The rest seems to work fine.
> So I gonna push forward with the Johnzon-1.0.1 release
> 
> Can anybody have a look at it?
> 
> txs and LieGrue,
> strub
> 
> 
> 
>> Am 04.05.2018 um 22:05 schrieb Mark Struberg >>> :
>> 
>> I've now also deployed fresh snapshots and will update in master
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 04.05.2018 um 21:53 schrieb Mark Struberg
>>> :
>>> 
>>> Yes, working on it.
>>> 
>>> But I only see 2 bugs reported for this release.
>>> 
>>> https://issues.apache.org/jira/projects/JOHNZON/versions/12340497
>>> 
>>> 
>>> JOHNZON-160 org.apache.johnzon.mapper.MapperException:
>>> ObjectConverters are only supported for Classes not TypesUnassigned
>>> Resolved
>>> JOHNZON-101 JsonObject#getJson* must not throw NullPointerException
>>> Reinhard Sandtner   Closed
>>> 
>>> 
>>> I now applied the patch - thanks again to Jon for doing all  the work!
>>> 
>>> I've also went through the changes (hack, that was a lot!) and tried
>>> to extract the ticket numbers:
>>> 
>>> https://issues.apache.org/jira/projects/JOHNZON/versions/12340497#release-report-tab-body
>>> 
>>> So I'm ready to roll the Johnzon-1.0.1 release ^^
>>> 
>>> Will keep you updated.
>>> 
>>> LieGrue,
>>> strub
>>> 
 Am 02.05.2018 um 22:45 schrieb Alex The Rocker >>> :
 
 Hello,
 
 Now that OWB-1.7.5 vote passed, how about Johnzon 1.0.1 for upcoming
 TomEE 7.0.5?
 Shouldn't there be a vote to officialize Johnzon 1.0.1?
 
 Best regards,
 Alexandre
 
 
 2018-04-29 13:04 GMT+02:00 Mark Struberg >>> :
> The OWB-1.7.5 vote is on the list now.
> 
> LieGrue,
> strub
> 
>> Am 27.04.2018 um 15:16 schrieb Romain Manni-Bucau <
>>> rmannibu...@gmail.com>:
>> 
>> We are working with Mark on a release train soon, johnzon would be
>>> part of
>> it probably.
>> An OWB release is needed too AFAIK and is on its way.
>> 
>> 
>> Romain Manni-Bucau
>> @rmannibucau  |  Blog
>>  | Old Blog
>>  | Github <
>>> https://github.com/rmannibucau> |
>> LinkedIn  | Book
>> <
>>> https://www.packtpub.com/application-development/java-ee-8-high-performance
 
>> 
>> 2018-04-27 14:43 GMT+02:00 Alex The Rocker :
>> 
>>> Hello TomEE developers,
>>> 
>>> I was away for a while, and I'm a bit lost on the TomEE 7.0.5
>>> upcoming
>>> release plans:
>>> - Jon did a great job with PR for upcoming Johnzon 1.0.1, but as
>>> far
>>> as I see, Johnzon 1.0.1 is still not released
>>> - What else would prevent TomEE 7.0.5 from being released?
>>> 
>>> As usual I volunteer for running heavy tests on any preview...
>>> 
>>> Best regards,
>>> Alexandre
>>> 
>>> 
>>> 2018-04-16