Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

Will review and apply later.

LieGrue,
Strub

> Am 16.04.2018 um 07:16 schrieb Romain Manni-Bucau :
> 
> (Indeed) +1 from me and thanks Jon for the huge work. Will wait some other
> member of the community review it since, as you mentionned, idea was coming
> from me but happy to apply it after.
> 
> Le 15 avr. 2018 22:28, "Jonathan Gallimore" 
> a écrit :
> 
>> Hi,
>> 
>> This discussion originated on the TomEE dev@ list, but I think it is more
>> appropriate that it continue here. Effectively I'm looking at trying to
>> provide a 1.0.1 version of Johnzon that is at the the same API level as
>> 1.0.0, but has all the fixes from master, that we can bundle with a TomEE 7
>> release.
>> 
>> I've opened up a PR here: https://github.com/apache/johnzon/pull/21, for
>> discussion. I'll attempt to cross-reference this back to the JIRAs fixed
>> over the next couple of days, but I'd welcome any feedback.
>> 
>> Many thanks
>> 
>> Jon
>> 
>> On Sun, Apr 1, 2018 at 6:04 PM, Jonathan Gallimore <
>> jonathan.gallim...@gmail.com> wrote:
>> 
>>> Happy to try that. I'll give that a go this evening. I misunderstood your
>>> proposal, but it makes sense now.
>>> 
>>> Cheers
>>> 
>>> Jo
>>> 
>>> On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
>>> 
>>> What about my proposal? Take johnzon master, copy it over 1.0.x and
>>> downgrade apis? It is probably the safest and shouldnt be long to make
>>> work. Can help next week if needed.
>>> 
>>> Le 1 avr. 2018 17:06, "Jonathan Gallimore" >> 
>>> a
>>> écrit :
>>> 
 Agreed. I'll start working on the list of fixes tonight.
 
 Jon
 
 On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
 wrote:
 
> Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
>>> Java8
> as min version).
> 
> And I'd also happily volunteer to release Johnzon-1.0.1.
> 
> BUT, first we need to check which Johnzon bugfixes are necessary to
> backport!
> Then let's create tickets for that version and solve them.
> 
> LieGrue,
> strub
> 
> 
>> Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
>> 
>> I think getting TomEE 8 out is obviously is preferred option. I
>> would
> still
>> like to maintain TomEE 7 for those that want it. I'd be happy to go
> through
>> JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> 
> 
 
>>> 
>>> 
>>> 
>> 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

(Indeed) +1 from me and thanks Jon for the huge work. Will wait some other
member of the community review it since, as you mentionned, idea was coming
from me but happy to apply it after.

Le 15 avr. 2018 22:28, "Jonathan Gallimore" 
a écrit :

> Hi,
>
> This discussion originated on the TomEE dev@ list, but I think it is more
> appropriate that it continue here. Effectively I'm looking at trying to
> provide a 1.0.1 version of Johnzon that is at the the same API level as
> 1.0.0, but has all the fixes from master, that we can bundle with a TomEE 7
> release.
>
> I've opened up a PR here: https://github.com/apache/johnzon/pull/21, for
> discussion. I'll attempt to cross-reference this back to the JIRAs fixed
> over the next couple of days, but I'd welcome any feedback.
>
> Many thanks
>
> Jon
>
> On Sun, Apr 1, 2018 at 6:04 PM, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > Happy to try that. I'll give that a go this evening. I misunderstood your
> > proposal, but it makes sense now.
> >
> > Cheers
> >
> > Jo
> >
> > On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
> >
> > What about my proposal? Take johnzon master, copy it over 1.0.x and
> > downgrade apis? It is probably the safest and shouldnt be long to make
> > work. Can help next week if needed.
> >
> > Le 1 avr. 2018 17:06, "Jonathan Gallimore"  >
> > a
> > écrit :
> >
> > > Agreed. I'll start working on the list of fixes tonight.
> > >
> > > Jon
> > >
> > > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> > > wrote:
> > >
> > > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
> > Java8
> > > > as min version).
> > > >
> > > > And I'd also happily volunteer to release Johnzon-1.0.1.
> > > >
> > > > BUT, first we need to check which Johnzon bugfixes are necessary to
> > > > backport!
> > > > Then let's create tickets for that version and solve them.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > > > jonathan.gallim...@gmail.com>:
> > > > >
> > > > > I think getting TomEE 8 out is obviously is preferred option. I
> would
> > > > still
> > > > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > > > through
> > > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> > > >
> > > >
> > >
> >
> >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

(Indeed) +1 from me and thanks Jon for the huge work. Will wait some other
member of the community review it since, as you mentionned, idea was coming
from me but happy to apply it after.

Le 15 avr. 2018 22:28, "Jonathan Gallimore" 
a écrit :

> Hi,
>
> This discussion originated on the TomEE dev@ list, but I think it is more
> appropriate that it continue here. Effectively I'm looking at trying to
> provide a 1.0.1 version of Johnzon that is at the the same API level as
> 1.0.0, but has all the fixes from master, that we can bundle with a TomEE 7
> release.
>
> I've opened up a PR here: https://github.com/apache/johnzon/pull/21, for
> discussion. I'll attempt to cross-reference this back to the JIRAs fixed
> over the next couple of days, but I'd welcome any feedback.
>
> Many thanks
>
> Jon
>
> On Sun, Apr 1, 2018 at 6:04 PM, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
>
> > Happy to try that. I'll give that a go this evening. I misunderstood your
> > proposal, but it makes sense now.
> >
> > Cheers
> >
> > Jo
> >
> > On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
> >
> > What about my proposal? Take johnzon master, copy it over 1.0.x and
> > downgrade apis? It is probably the safest and shouldnt be long to make
> > work. Can help next week if needed.
> >
> > Le 1 avr. 2018 17:06, "Jonathan Gallimore"  >
> > a
> > écrit :
> >
> > > Agreed. I'll start working on the list of fixes tonight.
> > >
> > > Jon
> > >
> > > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> > > wrote:
> > >
> > > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
> > Java8
> > > > as min version).
> > > >
> > > > And I'd also happily volunteer to release Johnzon-1.0.1.
> > > >
> > > > BUT, first we need to check which Johnzon bugfixes are necessary to
> > > > backport!
> > > > Then let's create tickets for that version and solve them.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > > > jonathan.gallim...@gmail.com>:
> > > > >
> > > > > I think getting TomEE 8 out is obviously is preferred option. I
> would
> > > > still
> > > > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > > > through
> > > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> > > >
> > > >
> > >
> >
> >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Hi,

This discussion originated on the TomEE dev@ list, but I think it is more
appropriate that it continue here. Effectively I'm looking at trying to
provide a 1.0.1 version of Johnzon that is at the the same API level as
1.0.0, but has all the fixes from master, that we can bundle with a TomEE 7
release.

I've opened up a PR here: https://github.com/apache/johnzon/pull/21, for
discussion. I'll attempt to cross-reference this back to the JIRAs fixed
over the next couple of days, but I'd welcome any feedback.

Many thanks

Jon

On Sun, Apr 1, 2018 at 6:04 PM, Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> Happy to try that. I'll give that a go this evening. I misunderstood your
> proposal, but it makes sense now.
>
> Cheers
>
> Jo
>
> On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
>
> What about my proposal? Take johnzon master, copy it over 1.0.x and
> downgrade apis? It is probably the safest and shouldnt be long to make
> work. Can help next week if needed.
>
> Le 1 avr. 2018 17:06, "Jonathan Gallimore" 
> a
> écrit :
>
> > Agreed. I'll start working on the list of fixes tonight.
> >
> > Jon
> >
> > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> > wrote:
> >
> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
> Java8
> > > as min version).
> > >
> > > And I'd also happily volunteer to release Johnzon-1.0.1.
> > >
> > > BUT, first we need to check which Johnzon bugfixes are necessary to
> > > backport!
> > > Then let's create tickets for that version and solve them.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > > jonathan.gallim...@gmail.com>:
> > > >
> > > > I think getting TomEE 8 out is obviously is preferred option. I would
> > > still
> > > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > > through
> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> > >
> > >
> >
>
>
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Not yet. Doing what I can. Last week and this weekend was extremely busy.

Jon

On Sun, 8 Apr 2018, 23:05 Alex The Rocker,  wrote:

> Hello Jon,
>
> Do you have some news to share with us about your efforts to release
> Johnzon-1.0.1 / TomEE+ 7.0.5 ?
>
> Thanks,
> Alexandre
>
> 2018-04-04 16:33 GMT+02:00 Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> > I'm about half-way through - couple of modules still to do and there's a
> > handful of test failures.
> >
> > Jon
> >
> > On Wed, Apr 4, 2018 at 3:25 PM, Alex The Rocker 
> > wrote:
> >
> >> Hello Jon,
> >>
> >> Have you got some news about this update for Johnzon-1.0.1 / TomEE
> 7.0.5 ?
> >> Anytime you have something ready for test, I'll test !
> >>
> >> Best regards,
> >> Alexandre
> >>
> >>
> >> 2018-04-02 1:56 GMT+02:00 Jonathan Gallimore <
> jonathan.gallim...@gmail.com
> >> >:
> >> > Made some progress with this - more tomorrow.
> >> >
> >> > Jon
> >> >
> >> > On Sun, 1 Apr 2018, 18:04 Jonathan Gallimore, <
> >> jonathan.gallim...@gmail.com>
> >> > wrote:
> >> >
> >> >> Happy to try that. I'll give that a go this evening. I misunderstood
> >> your
> >> >> proposal, but it makes sense now.
> >> >>
> >> >> Cheers
> >> >>
> >> >> Jo
> >> >>
> >> >> On 1 Apr 2018 17:41, "Romain Manni-Bucau" 
> >> wrote:
> >> >>
> >> >> What about my proposal? Take johnzon master, copy it over 1.0.x and
> >> >> downgrade apis? It is probably the safest and shouldnt be long to
> make
> >> >> work. Can help next week if needed.
> >> >>
> >> >> Le 1 avr. 2018 17:06, "Jonathan Gallimore" <
> >> jonathan.gallim...@gmail.com>
> >> >> a
> >> >> écrit :
> >> >>
> >> >> > Agreed. I'll start working on the list of fixes tonight.
> >> >> >
> >> >> > Jon
> >> >> >
> >> >> > On Sun, 1 Apr 2018, 16:02 Mark Struberg,  >
> >> >> > wrote:
> >> >> >
> >> >> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up
> to
> >> >> Java8
> >> >> > > as min version).
> >> >> > >
> >> >> > > And I'd also happily volunteer to release Johnzon-1.0.1.
> >> >> > >
> >> >> > > BUT, first we need to check which Johnzon bugfixes are necessary
> to
> >> >> > > backport!
> >> >> > > Then let's create tickets for that version and solve them.
> >> >> > >
> >> >> > > LieGrue,
> >> >> > > strub
> >> >> > >
> >> >> > >
> >> >> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> >> >> > > jonathan.gallim...@gmail.com>:
> >> >> > > >
> >> >> > > > I think getting TomEE 8 out is obviously is preferred option. I
> >> would
> >> >> > > still
> >> >> > > > like to maintain TomEE 7 for those that want it. I'd be happy
> to
> >> go
> >> >> > > through
> >> >> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Jon,

Do you have some news to share with us about your efforts to release
Johnzon-1.0.1 / TomEE+ 7.0.5 ?

Thanks,
Alexandre

2018-04-04 16:33 GMT+02:00 Jonathan Gallimore :
> I'm about half-way through - couple of modules still to do and there's a
> handful of test failures.
>
> Jon
>
> On Wed, Apr 4, 2018 at 3:25 PM, Alex The Rocker 
> wrote:
>
>> Hello Jon,
>>
>> Have you got some news about this update for Johnzon-1.0.1 / TomEE 7.0.5 ?
>> Anytime you have something ready for test, I'll test !
>>
>> Best regards,
>> Alexandre
>>
>>
>> 2018-04-02 1:56 GMT+02:00 Jonathan Gallimore > >:
>> > Made some progress with this - more tomorrow.
>> >
>> > Jon
>> >
>> > On Sun, 1 Apr 2018, 18:04 Jonathan Gallimore, <
>> jonathan.gallim...@gmail.com>
>> > wrote:
>> >
>> >> Happy to try that. I'll give that a go this evening. I misunderstood
>> your
>> >> proposal, but it makes sense now.
>> >>
>> >> Cheers
>> >>
>> >> Jo
>> >>
>> >> On 1 Apr 2018 17:41, "Romain Manni-Bucau" 
>> wrote:
>> >>
>> >> What about my proposal? Take johnzon master, copy it over 1.0.x and
>> >> downgrade apis? It is probably the safest and shouldnt be long to make
>> >> work. Can help next week if needed.
>> >>
>> >> Le 1 avr. 2018 17:06, "Jonathan Gallimore" <
>> jonathan.gallim...@gmail.com>
>> >> a
>> >> écrit :
>> >>
>> >> > Agreed. I'll start working on the list of fixes tonight.
>> >> >
>> >> > Jon
>> >> >
>> >> > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
>> >> > wrote:
>> >> >
>> >> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
>> >> Java8
>> >> > > as min version).
>> >> > >
>> >> > > And I'd also happily volunteer to release Johnzon-1.0.1.
>> >> > >
>> >> > > BUT, first we need to check which Johnzon bugfixes are necessary to
>> >> > > backport!
>> >> > > Then let's create tickets for that version and solve them.
>> >> > >
>> >> > > LieGrue,
>> >> > > strub
>> >> > >
>> >> > >
>> >> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
>> >> > > jonathan.gallim...@gmail.com>:
>> >> > > >
>> >> > > > I think getting TomEE 8 out is obviously is preferred option. I
>> would
>> >> > > still
>> >> > > > like to maintain TomEE 7 for those that want it. I'd be happy to
>> go
>> >> > > through
>> >> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

I'm about half-way through - couple of modules still to do and there's a
handful of test failures.

Jon

On Wed, Apr 4, 2018 at 3:25 PM, Alex The Rocker 
wrote:

> Hello Jon,
>
> Have you got some news about this update for Johnzon-1.0.1 / TomEE 7.0.5 ?
> Anytime you have something ready for test, I'll test !
>
> Best regards,
> Alexandre
>
>
> 2018-04-02 1:56 GMT+02:00 Jonathan Gallimore  >:
> > Made some progress with this - more tomorrow.
> >
> > Jon
> >
> > On Sun, 1 Apr 2018, 18:04 Jonathan Gallimore, <
> jonathan.gallim...@gmail.com>
> > wrote:
> >
> >> Happy to try that. I'll give that a go this evening. I misunderstood
> your
> >> proposal, but it makes sense now.
> >>
> >> Cheers
> >>
> >> Jo
> >>
> >> On 1 Apr 2018 17:41, "Romain Manni-Bucau" 
> wrote:
> >>
> >> What about my proposal? Take johnzon master, copy it over 1.0.x and
> >> downgrade apis? It is probably the safest and shouldnt be long to make
> >> work. Can help next week if needed.
> >>
> >> Le 1 avr. 2018 17:06, "Jonathan Gallimore" <
> jonathan.gallim...@gmail.com>
> >> a
> >> écrit :
> >>
> >> > Agreed. I'll start working on the list of fixes tonight.
> >> >
> >> > Jon
> >> >
> >> > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> >> > wrote:
> >> >
> >> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
> >> Java8
> >> > > as min version).
> >> > >
> >> > > And I'd also happily volunteer to release Johnzon-1.0.1.
> >> > >
> >> > > BUT, first we need to check which Johnzon bugfixes are necessary to
> >> > > backport!
> >> > > Then let's create tickets for that version and solve them.
> >> > >
> >> > > LieGrue,
> >> > > strub
> >> > >
> >> > >
> >> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> >> > > jonathan.gallim...@gmail.com>:
> >> > > >
> >> > > > I think getting TomEE 8 out is obviously is preferred option. I
> would
> >> > > still
> >> > > > like to maintain TomEE 7 for those that want it. I'd be happy to
> go
> >> > > through
> >> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Jon,

Have you got some news about this update for Johnzon-1.0.1 / TomEE 7.0.5 ?
Anytime you have something ready for test, I'll test !

Best regards,
Alexandre


2018-04-02 1:56 GMT+02:00 Jonathan Gallimore :
> Made some progress with this - more tomorrow.
>
> Jon
>
> On Sun, 1 Apr 2018, 18:04 Jonathan Gallimore, 
> wrote:
>
>> Happy to try that. I'll give that a go this evening. I misunderstood your
>> proposal, but it makes sense now.
>>
>> Cheers
>>
>> Jo
>>
>> On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
>>
>> What about my proposal? Take johnzon master, copy it over 1.0.x and
>> downgrade apis? It is probably the safest and shouldnt be long to make
>> work. Can help next week if needed.
>>
>> Le 1 avr. 2018 17:06, "Jonathan Gallimore" 
>> a
>> écrit :
>>
>> > Agreed. I'll start working on the list of fixes tonight.
>> >
>> > Jon
>> >
>> > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
>> > wrote:
>> >
>> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
>> Java8
>> > > as min version).
>> > >
>> > > And I'd also happily volunteer to release Johnzon-1.0.1.
>> > >
>> > > BUT, first we need to check which Johnzon bugfixes are necessary to
>> > > backport!
>> > > Then let's create tickets for that version and solve them.
>> > >
>> > > LieGrue,
>> > > strub
>> > >
>> > >
>> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
>> > > jonathan.gallim...@gmail.com>:
>> > > >
>> > > > I think getting TomEE 8 out is obviously is preferred option. I would
>> > > still
>> > > > like to maintain TomEE 7 for those that want it. I'd be happy to go
>> > > through
>> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
>> > >
>> > >
>> >
>>
>>
>>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Made some progress with this - more tomorrow.

Jon

On Sun, 1 Apr 2018, 18:04 Jonathan Gallimore, 
wrote:

> Happy to try that. I'll give that a go this evening. I misunderstood your
> proposal, but it makes sense now.
>
> Cheers
>
> Jo
>
> On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:
>
> What about my proposal? Take johnzon master, copy it over 1.0.x and
> downgrade apis? It is probably the safest and shouldnt be long to make
> work. Can help next week if needed.
>
> Le 1 avr. 2018 17:06, "Jonathan Gallimore" 
> a
> écrit :
>
> > Agreed. I'll start working on the list of fixes tonight.
> >
> > Jon
> >
> > On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> > wrote:
> >
> > > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to
> Java8
> > > as min version).
> > >
> > > And I'd also happily volunteer to release Johnzon-1.0.1.
> > >
> > > BUT, first we need to check which Johnzon bugfixes are necessary to
> > > backport!
> > > Then let's create tickets for that version and solve them.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > > jonathan.gallim...@gmail.com>:
> > > >
> > > > I think getting TomEE 8 out is obviously is preferred option. I would
> > > still
> > > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > > through
> > > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> > >
> > >
> >
>
>
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Happy to try that. I'll give that a go this evening. I misunderstood your
proposal, but it makes sense now.

Cheers

Jo

On 1 Apr 2018 17:41, "Romain Manni-Bucau"  wrote:

What about my proposal? Take johnzon master, copy it over 1.0.x and
downgrade apis? It is probably the safest and shouldnt be long to make
work. Can help next week if needed.

Le 1 avr. 2018 17:06, "Jonathan Gallimore"  a
écrit :

> Agreed. I'll start working on the list of fixes tonight.
>
> Jon
>
> On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> wrote:
>
> > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8
> > as min version).
> >
> > And I'd also happily volunteer to release Johnzon-1.0.1.
> >
> > BUT, first we need to check which Johnzon bugfixes are necessary to
> > backport!
> > Then let's create tickets for that version and solve them.
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>:
> > >
> > > I think getting TomEE 8 out is obviously is preferred option. I would
> > still
> > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > through
> > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hi Romain,

Whatever works will be great!

Alexandre

2018-04-01 18:40 GMT+02:00 Romain Manni-Bucau :
> What about my proposal? Take johnzon master, copy it over 1.0.x and
> downgrade apis? It is probably the safest and shouldnt be long to make
> work. Can help next week if needed.
>
> Le 1 avr. 2018 17:06, "Jonathan Gallimore"  a
> écrit :
>
>> Agreed. I'll start working on the list of fixes tonight.
>>
>> Jon
>>
>> On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
>> wrote:
>>
>> > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8
>> > as min version).
>> >
>> > And I'd also happily volunteer to release Johnzon-1.0.1.
>> >
>> > BUT, first we need to check which Johnzon bugfixes are necessary to
>> > backport!
>> > Then let's create tickets for that version and solve them.
>> >
>> > LieGrue,
>> > strub
>> >
>> >
>> > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
>> > jonathan.gallim...@gmail.com>:
>> > >
>> > > I think getting TomEE 8 out is obviously is preferred option. I would
>> > still
>> > > like to maintain TomEE 7 for those that want it. I'd be happy to go
>> > through
>> > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
>> >
>> >
>>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Jon,

First of all, thank you very much for your kind proposal for the release job!

To clarified what's expected on my side in a TomEE 7.0.5 release:
 * I have re-updated https://issues.apache.org/jira/browse/TOMEE-2153
to ask for TomEE 7.0.5 dependency upgrade to Johnzon 1.0.1.
 * In this Johnzon 1.0.1, I need at least fixes for these JIRAs:
https://issues.apache.org/jira/browse/JOHNZON-101  (supposed to be closed)
https://issues.apache.org/jira/browse/JOHNZON-158  (backport needed)
https://issues.apache.org/jira/browse/JOHNZON-149  (supposed to be closed)
provided that this later is supposed to fix this one:
https://issues.apache.org/jira/browse/JOHNZON-160  (closed as
duplicate of JOHNZON-149)

I will test any available snapshot/Release Candidate of Johnzon 1.0.1
that you can provide (please send download links).

Thanks!

PS: I'd love to move to TomEE 8 ASAP, but sometimes there are
constraints, well that's life...

Alexandre



2018-04-01 17:06 GMT+02:00 Jonathan Gallimore :
> Agreed. I'll start working on the list of fixes tonight.
>
> Jon
>
> On Sun, 1 Apr 2018, 16:02 Mark Struberg,  wrote:
>
>> Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8
>> as min version).
>>
>> And I'd also happily volunteer to release Johnzon-1.0.1.
>>
>> BUT, first we need to check which Johnzon bugfixes are necessary to
>> backport!
>> Then let's create tickets for that version and solve them.
>>
>> LieGrue,
>> strub
>>
>>
>> > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
>> jonathan.gallim...@gmail.com>:
>> >
>> > I think getting TomEE 8 out is obviously is preferred option. I would
>> still
>> > like to maintain TomEE 7 for those that want it. I'd be happy to go
>> through
>> > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
>>
>>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

What about my proposal? Take johnzon master, copy it over 1.0.x and
downgrade apis? It is probably the safest and shouldnt be long to make
work. Can help next week if needed.

Le 1 avr. 2018 17:06, "Jonathan Gallimore"  a
écrit :

> Agreed. I'll start working on the list of fixes tonight.
>
> Jon
>
> On Sun, 1 Apr 2018, 16:02 Mark Struberg, 
> wrote:
>
> > Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8
> > as min version).
> >
> > And I'd also happily volunteer to release Johnzon-1.0.1.
> >
> > BUT, first we need to check which Johnzon bugfixes are necessary to
> > backport!
> > Then let's create tickets for that version and solve them.
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>:
> > >
> > > I think getting TomEE 8 out is obviously is preferred option. I would
> > still
> > > like to maintain TomEE 7 for those that want it. I'd be happy to go
> > through
> > > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
> >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Agreed. I'll start working on the list of fixes tonight.

Jon

On Sun, 1 Apr 2018, 16:02 Mark Struberg,  wrote:

> Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8
> as min version).
>
> And I'd also happily volunteer to release Johnzon-1.0.1.
>
> BUT, first we need to check which Johnzon bugfixes are necessary to
> backport!
> Then let's create tickets for that version and solve them.
>
> LieGrue,
> strub
>
>
> > Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >
> > I think getting TomEE 8 out is obviously is preferred option. I would
> still
> > like to maintain TomEE 7 for those that want it. I'd be happy to go
> through
> > JIRA, and backport fixes as necessary for Johnzon 1.0.x.
>
>

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

Of course I also want to ship a 7.0.5 (or 7.1.0 if we opt to up to Java8 as min 
version).

And I'd also happily volunteer to release Johnzon-1.0.1. 

BUT, first we need to check which Johnzon bugfixes are necessary to backport!
Then let's create tickets for that version and solve them.

LieGrue,
strub


> Am 01.04.2018 um 16:50 schrieb Jonathan Gallimore 
> :
> 
> I think getting TomEE 8 out is obviously is preferred option. I would still
> like to maintain TomEE 7 for those that want it. I'd be happy to go through
> JIRA, and backport fixes as necessary for Johnzon 1.0.x.

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

I think getting TomEE 8 out is obviously is preferred option. I would still
like to maintain TomEE 7 for those that want it. I'd be happy to go through
JIRA, and backport fixes as necessary for Johnzon 1.0.x.

Jon

On Sun, 1 Apr 2018, 11:03 Mark Struberg,  wrote:

> The problem is that adding Johnzon-1.1.7 to TomEE7 _without_ also updating
> the jsonp spec to 1.1 will NOT work!
> It will blow up with MethodNotFoundExceptions...
>
> What is needed is the following:We need a list of bugs in johnzon-1.0.0
> which got fixed in the 8 EE8 releases we did so far (johnzon-1.1.0..
> 1.1.7).Then we can look which one can easily get backported and which
> others would be complicated.
> And again: EVERY HELPING HAND IS WELCOME!
> Yes, most of you are interested primarily in TomEE, but lots of the hard
> work is done also in other projects!Don't be afraid, the Johnzon people
> will not bite you if you help them ;)
> I've seen https://issues.apache.org/jira/browse/JOHNZON-149Is this one
> ticket referenced there the only thing we would need for TomEE7? In that
> case I could run the Johnzon-1.0.1 release today.But what else do we need?
> Is there a TomEE ticket which explains what's missing?
>
> LieGrue,strub
>
>
> On Sunday, 1 April 2018, 08:59:03 CEST, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
>
>  Le 1 avr. 2018 07:47, "Alex The Rocker"  a écrit :
>
> Hello Mark,
>
> The point is not to enable EE8 features in TomEE 7.0.5.
> Is is about fixing the many issues of currently available TomEE 7.0.4
> in its JSON-P 1.0 *implementation*.
>
> With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
> because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
> is "just" the *implementation* of JSON-P in TomEE  since TomEE version
> 7.
>
>
> No you need the api too.
>
>
> My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
> fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
> way than trying to sort out which Johnzon 1.1.7 fixes could be
> backported to Johnzon 1.0.1.
>
>
> The fear here is a partial backport or more delay for 7.0.5.
>
>
> I find this proposal quite reasonable.
>
> In addition, I have to mention that I know couple of developers who
> hacked around couple of JPSON issues they got with TomEE 7.0.4 by
> replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
> would make non-hackers more comfortable with TomEE 7.
>
>
>
> Same here
>
>
>
>
>  I am not part of TomEE contributors, so of course all this is suggestions.
> What is the process for deciding on whether or not Johnzon 1.1.7 would
> be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?
>
>
> That said Mark is right and why i proposed to just use tomee 8 which is a
> smooth upgrade
>
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 23:34 GMT+02:00 Mark Struberg :
> > If we start adding EE8 features then we will further blur the line.Imo we
> should remain clean and push for TomEE8 instead...
> > LieGrue,strub
> >
> >
> >On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
> >
> >  Le 31 mars 2018 22:33, "Mark Struberg"  a
> écrit :
> >
> > folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> > include this in Tomee7 (seven!)?
> > I don't think so...
> >
> >
> > Why? Doesnt prevent to be ee7 certified + we are not so only constraint
> is
> > about java min version.
> >
> > That said agree tomee 8 can be safer for a long terms choice.
> >
> > LieGrue,strub
> >
> >
> >On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> > alex.m3...@gmail.com> wrote:
> >
> >  Hello,
> >
> > To continue on this thread: I have updated
> > https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> > explicit.
> > New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
> >
> > Could this be part of next 7.0.5-snapshot ?
> >
> > Best regards,
> > Alexandre
> >
> >
> > 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
> >> Le 31 mars 2018 16:36, "Alex The Rocker"  a
> écrit :
> >>
> >> Hi Romain,
> >>
> >> Are you suggesting that instead of waiting for TomEE 7.0.5 people
> >> should upgrade to TomEE 8 ?
> >>
> >>
> >> Yes
> >>
> >>
> >> IHMO it's a bigger step for people : major version changes usually
> >> involves major impacts (at least that's my experience).
> >>
> >>
> >> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1
> to
> >> 7. Here it should even be smoother.
> >>
> >> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
> >> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
> >> 1.1.x to get all the fixes committed so far.
> >>
> >>
> >> +1 from me too
> >>
> >> After all ,Java 7 end of public updates was in April 2015, so making
> >> Java 8 as the minimum 

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

Many downstream projects have a mixture of tomee-javaee-api and geronimo-specs.
So if someone e.g. has a geronimo-jsonp_1.0_spec.jar or javax.json-1.0.jar in 
his project then it will blow up.
LieGrue,strub
 

On Sunday, 1 April 2018, 16:13:00 CEST, Romain Manni-Bucau 
 wrote:  
 
 Le 1 avr. 2018 12:13, "Mark Struberg"  a écrit :

> No, if you read back the proposal (wzs months ago now) > we would have
updated javaee api jar too.
That would trash tons of downstream users which use openejb-core in their
unit tests :(


Nop, why? You are thinking of an explicit javaee staying to 7? Upgrading
openejb can need to upgrade javaee api anyway (for bugfixes) so not a
blocker by itself.

That said, once again, tomee 8 option is saner.

LieGrue,strub

  On Sunday, 1 April 2018, 12:03:23 CEST, Mark Struberg
 wrote:

 The problem is that adding Johnzon-1.1.7 to TomEE7 _without_ also updating
the jsonp spec to 1.1 will NOT work!
It will blow up with MethodNotFoundExceptions...

What is needed is the following:We need a list of bugs in johnzon-1.0.0
which got fixed in the 8 EE8 releases we did so far (johnzon-1.1.0..
1.1.7).Then we can look which one can easily get backported and which
others would be complicated.
And again: EVERY HELPING HAND IS WELCOME!
Yes, most of you are interested primarily in TomEE, but lots of the hard
work is done also in other projects!Don't be afraid, the Johnzon people
will not bite you if you help them ;)
I've seen https://issues.apache.org/jira/browse/JOHNZON-149Is this one
ticket referenced there the only thing we would need for TomEE7? In that
case I could run the Johnzon-1.0.1 release today.But what else do we need?
Is there a TomEE ticket which explains what's missing?

LieGrue,strub


    On Sunday, 1 April 2018, 08:59:03 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:

 Le 1 avr. 2018 07:47, "Alex The Rocker"  a écrit :

Hello Mark,

The point is not to enable EE8 features in TomEE 7.0.5.
Is is about fixing the many issues of currently available TomEE 7.0.4
in its JSON-P 1.0 *implementation*.

With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
is "just" the *implementation* of JSON-P in TomEE  since TomEE version
7.


No you need the api too.


My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
way than trying to sort out which Johnzon 1.1.7 fixes could be
backported to Johnzon 1.0.1.


The fear here is a partial backport or more delay for 7.0.5.


I find this proposal quite reasonable.

In addition, I have to mention that I know couple of developers who
hacked around couple of JPSON issues they got with TomEE 7.0.4 by
replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
would make non-hackers more comfortable with TomEE 7.



Same here




 I am not part of TomEE contributors, so of course all this is suggestions.
What is the process for deciding on whether or not Johnzon 1.1.7 would
be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?


That said Mark is right and why i proposed to just use tomee 8 which is a
smooth upgrade


Best regards,
Alexandre


2018-03-31 23:34 GMT+02:00 Mark Struberg :
> If we start adding EE8 features then we will further blur the line.Imo we
should remain clean and push for TomEE8 instead...
> LieGrue,strub
>
>
>    On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:
>
>  Le 31 mars 2018 22:33, "Mark Struberg"  a
écrit :
>
> folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> include this in Tomee7 (seven!)?
> I don't think so...
>
>
> Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
> about java min version.
>
> That said agree tomee 8 can be safer for a long terms choice.
>
> LieGrue,strub
>
>
>    On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> alex.m3...@gmail.com> wrote:
>
>  Hello,
>
> To continue on this thread: I have updated
> https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> explicit.
> New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
>
> Could this be part of next 7.0.5-snapshot ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>>
>> Hi Romain,
>>
>> Are you suggesting that instead of waiting for TomEE 7.0.5 people
>> should upgrade to TomEE 8 ?
>>
>>
>> Yes
>>
>>
>> IHMO it's a bigger step for people : major version changes usually
>> involves major impacts (at least that's my experience).
>>
>>
>> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1
to
>> 7. Here it should even 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Le 1 avr. 2018 12:13, "Mark Struberg"  a écrit :

> No, if you read back the proposal (wzs months ago now) > we would have
updated javaee api jar too.
That would trash tons of downstream users which use openejb-core in their
unit tests :(


Nop, why? You are thinking of an explicit javaee staying to 7? Upgrading
openejb can need to upgrade javaee api anyway (for bugfixes) so not a
blocker by itself.

That said, once again, tomee 8 option is saner.

LieGrue,strub

   On Sunday, 1 April 2018, 12:03:23 CEST, Mark Struberg
 wrote:

 The problem is that adding Johnzon-1.1.7 to TomEE7 _without_ also updating
the jsonp spec to 1.1 will NOT work!
It will blow up with MethodNotFoundExceptions...

What is needed is the following:We need a list of bugs in johnzon-1.0.0
which got fixed in the 8 EE8 releases we did so far (johnzon-1.1.0..
1.1.7).Then we can look which one can easily get backported and which
others would be complicated.
And again: EVERY HELPING HAND IS WELCOME!
Yes, most of you are interested primarily in TomEE, but lots of the hard
work is done also in other projects!Don't be afraid, the Johnzon people
will not bite you if you help them ;)
I've seen https://issues.apache.org/jira/browse/JOHNZON-149Is this one
ticket referenced there the only thing we would need for TomEE7? In that
case I could run the Johnzon-1.0.1 release today.But what else do we need?
Is there a TomEE ticket which explains what's missing?

LieGrue,strub


On Sunday, 1 April 2018, 08:59:03 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:

 Le 1 avr. 2018 07:47, "Alex The Rocker"  a écrit :

Hello Mark,

The point is not to enable EE8 features in TomEE 7.0.5.
Is is about fixing the many issues of currently available TomEE 7.0.4
in its JSON-P 1.0 *implementation*.

With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
is "just" the *implementation* of JSON-P in TomEE  since TomEE version
7.


No you need the api too.


My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
way than trying to sort out which Johnzon 1.1.7 fixes could be
backported to Johnzon 1.0.1.


The fear here is a partial backport or more delay for 7.0.5.


I find this proposal quite reasonable.

In addition, I have to mention that I know couple of developers who
hacked around couple of JPSON issues they got with TomEE 7.0.4 by
replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
would make non-hackers more comfortable with TomEE 7.



Same here




 I am not part of TomEE contributors, so of course all this is suggestions.
What is the process for deciding on whether or not Johnzon 1.1.7 would
be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?


That said Mark is right and why i proposed to just use tomee 8 which is a
smooth upgrade


Best regards,
Alexandre


2018-03-31 23:34 GMT+02:00 Mark Struberg :
> If we start adding EE8 features then we will further blur the line.Imo we
should remain clean and push for TomEE8 instead...
> LieGrue,strub
>
>
>On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:
>
>  Le 31 mars 2018 22:33, "Mark Struberg"  a
écrit :
>
> folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> include this in Tomee7 (seven!)?
> I don't think so...
>
>
> Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
> about java min version.
>
> That said agree tomee 8 can be safer for a long terms choice.
>
> LieGrue,strub
>
>
>On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> alex.m3...@gmail.com> wrote:
>
>  Hello,
>
> To continue on this thread: I have updated
> https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> explicit.
> New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
>
> Could this be part of next 7.0.5-snapshot ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>>
>> Hi Romain,
>>
>> Are you suggesting that instead of waiting for TomEE 7.0.5 people
>> should upgrade to TomEE 8 ?
>>
>>
>> Yes
>>
>>
>> IHMO it's a bigger step for people : major version changes usually
>> involves major impacts (at least that's my experience).
>>
>>
>> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1
to
>> 7. Here it should even be smoother.
>>
>> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
>> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
>> 1.1.x to get all the fixes committed so far.
>>
>>
>> +1 from me too
>>
>> After all ,Java 7 end of public updates was in April 2015, so making

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

The problem is that adding Johnzon-1.1.7 to TomEE7 _without_ also updating the 
jsonp spec to 1.1 will NOT work!
It will blow up with MethodNotFoundExceptions...

What is needed is the following:We need a list of bugs in johnzon-1.0.0 which 
got fixed in the 8 EE8 releases we did so far (johnzon-1.1.0.. 1.1.7).Then we 
can look which one can easily get backported and which others would be 
complicated. 
And again: EVERY HELPING HAND IS WELCOME! 
Yes, most of you are interested primarily in TomEE, but lots of the hard work 
is done also in other projects!Don't be afraid, the Johnzon people will not 
bite you if you help them ;)
I've seen https://issues.apache.org/jira/browse/JOHNZON-149Is this one ticket 
referenced there the only thing we would need for TomEE7? In that case I could 
run the Johnzon-1.0.1 release today.But what else do we need?
Is there a TomEE ticket which explains what's missing?

LieGrue,strub
 

On Sunday, 1 April 2018, 08:59:03 CEST, Romain Manni-Bucau 
 wrote:  
 
 Le 1 avr. 2018 07:47, "Alex The Rocker"  a écrit :

Hello Mark,

The point is not to enable EE8 features in TomEE 7.0.5.
Is is about fixing the many issues of currently available TomEE 7.0.4
in its JSON-P 1.0 *implementation*.

With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
is "just" the *implementation* of JSON-P in TomEE  since TomEE version
7.


No you need the api too.


My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
way than trying to sort out which Johnzon 1.1.7 fixes could be
backported to Johnzon 1.0.1.


The fear here is a partial backport or more delay for 7.0.5.


I find this proposal quite reasonable.

In addition, I have to mention that I know couple of developers who
hacked around couple of JPSON issues they got with TomEE 7.0.4 by
replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
would make non-hackers more comfortable with TomEE 7.



Same here




 I am not part of TomEE contributors, so of course all this is suggestions.
What is the process for deciding on whether or not Johnzon 1.1.7 would
be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?


That said Mark is right and why i proposed to just use tomee 8 which is a
smooth upgrade


Best regards,
Alexandre


2018-03-31 23:34 GMT+02:00 Mark Struberg :
> If we start adding EE8 features then we will further blur the line.Imo we
should remain clean and push for TomEE8 instead...
> LieGrue,strub
>
>
>    On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:
>
>  Le 31 mars 2018 22:33, "Mark Struberg"  a
écrit :
>
> folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> include this in Tomee7 (seven!)?
> I don't think so...
>
>
> Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
> about java min version.
>
> That said agree tomee 8 can be safer for a long terms choice.
>
> LieGrue,strub
>
>
>    On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> alex.m3...@gmail.com> wrote:
>
>  Hello,
>
> To continue on this thread: I have updated
> https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> explicit.
> New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
>
> Could this be part of next 7.0.5-snapshot ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>>
>> Hi Romain,
>>
>> Are you suggesting that instead of waiting for TomEE 7.0.5 people
>> should upgrade to TomEE 8 ?
>>
>>
>> Yes
>>
>>
>> IHMO it's a bigger step for people : major version changes usually
>> involves major impacts (at least that's my experience).
>>
>>
>> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1
to
>> 7. Here it should even be smoother.
>>
>> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
>> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
>> 1.1.x to get all the fixes committed so far.
>>
>>
>> +1 from me too
>>
>> After all ,Java 7 end of public updates was in April 2015, so making
>> Java 8 as the minimum prerequisite for TomEE7 three years later after
>> this date sounds very reasonable.
>>
>> Thanks,
>> Alexandre
>>
>>
>>
>>
>> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>>> Le 31 mars 2018 15:00, "Jonathan Gallimore" <
jonathan.gallim...@gmail.com
>>
>>> a écrit :
>>>
>>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>>
>>> I'm not fussed either way, but we should discuss it and encourage input
>>> from the wider community. I'm sure I've asked before if it's ok to
> require
>>> Java 8 and still 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Le 1 avr. 2018 07:47, "Alex The Rocker"  a écrit :

Hello Mark,

The point is not to enable EE8 features in TomEE 7.0.5.
Is is about fixing the many issues of currently available TomEE 7.0.4
in its JSON-P 1.0 *implementation*.

With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
is "just" the *implementation* of JSON-P in TomEE  since TomEE version
7.


No you need the api too.


My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
way than trying to sort out which Johnzon 1.1.7 fixes could be
backported to Johnzon 1.0.1.


The fear here is a partial backport or more delay for 7.0.5.


I find this proposal quite reasonable.

In addition, I have to mention that I know couple of developers who
hacked around couple of JPSON issues they got with TomEE 7.0.4 by
replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
would make non-hackers more comfortable with TomEE 7.



Same here




 I am not part of TomEE contributors, so of course all this is suggestions.
What is the process for deciding on whether or not Johnzon 1.1.7 would
be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?


That said Mark is right and why i proposed to just use tomee 8 which is a
smooth upgrade


Best regards,
Alexandre


2018-03-31 23:34 GMT+02:00 Mark Struberg :
> If we start adding EE8 features then we will further blur the line.Imo we
should remain clean and push for TomEE8 instead...
> LieGrue,strub
>
>
> On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau <
rmannibu...@gmail.com> wrote:
>
>  Le 31 mars 2018 22:33, "Mark Struberg"  a
écrit :
>
> folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> include this in Tomee7 (seven!)?
> I don't think so...
>
>
> Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
> about java min version.
>
> That said agree tomee 8 can be safer for a long terms choice.
>
> LieGrue,strub
>
>
> On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> alex.m3...@gmail.com> wrote:
>
>  Hello,
>
> To continue on this thread: I have updated
> https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> explicit.
> New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
>
> Could this be part of next 7.0.5-snapshot ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>>
>> Hi Romain,
>>
>> Are you suggesting that instead of waiting for TomEE 7.0.5 people
>> should upgrade to TomEE 8 ?
>>
>>
>> Yes
>>
>>
>> IHMO it's a bigger step for people : major version changes usually
>> involves major impacts (at least that's my experience).
>>
>>
>> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1
to
>> 7. Here it should even be smoother.
>>
>> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
>> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
>> 1.1.x to get all the fixes committed so far.
>>
>>
>> +1 from me too
>>
>> After all ,Java 7 end of public updates was in April 2015, so making
>> Java 8 as the minimum prerequisite for TomEE7 three years later after
>> this date sounds very reasonable.
>>
>> Thanks,
>> Alexandre
>>
>>
>>
>>
>> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>>> Le 31 mars 2018 15:00, "Jonathan Gallimore" <
jonathan.gallim...@gmail.com
>>
>>> a écrit :
>>>
>>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>>
>>> I'm not fussed either way, but we should discuss it and encourage input
>>> from the wider community. I'm sure I've asked before if it's ok to
> require
>>> Java 8 and still target EE 7, but I can't remember if it was
definitively
>>> answered or not, and if it was, I can't remember what the answer was.
>>>
>>>
>>> Mixed thread.
>>>
>>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>>> ignore this one and upgrade straight after. Just thinking out loud.
>>>
>>>
>>> Jon
>>>
>>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker, 
wrote:
>>>
 Hello,

 I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
 Johnzon 1.1.x ?

 Best regards,
 Alexandre


 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
 > We can but we miss (ATM) a looot of fixes.
 >
 > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
 jonathan.gallim...@gmail.com>
 > a écrit :
 >
 >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7?
Looks
 like
 >> the code is in the branch and ready to go.
 >>
 >> Jon
 >>
 >> On Fri, Mar 30, 2018 at 9:03 AM, Alex 

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Mark,

The point is not to enable EE8 features in TomEE 7.0.5.
Is is about fixing the many issues of currently available TomEE 7.0.4
in its JSON-P 1.0 *implementation*.

With Johnzon 1.1.7, TomEE 7.0.5 will remains at EE7 compatiblity level
because there's no plan to include EE8 *interfaces* in 7.0.5: Johnzon
is "just" the *implementation* of JSON-P in TomEE  since TomEE version
7.

My understanding of Romain's proposal is that Johnzon 1.1.7 can fix
fhe current issues of JSON-P 1.0 in TomEE 7.0.5 in a more efficient
way than trying to sort out which Johnzon 1.1.7 fixes could be
backported to Johnzon 1.0.1.

I find this proposal quite reasonable.

In addition, I have to mention that I know couple of developers who
hacked around couple of JPSON issues they got with TomEE 7.0.4 by
replacing Johnzon with 1.1.x. Make this is official in TomEE 7.0.5
would make non-hackers more comfortable with TomEE 7.

 I am not part of TomEE contributors, so of course all this is suggestions.
What is the process for deciding on whether or not Johnzon 1.1.7 would
be the JSON-P implementation of TomEE 7.0.5? A vote by binding people?

Best regards,
Alexandre


2018-03-31 23:34 GMT+02:00 Mark Struberg :
> If we start adding EE8 features then we will further blur the line.Imo we 
> should remain clean and push for TomEE8 instead...
> LieGrue,strub
>
>
> On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau 
>  wrote:
>
>  Le 31 mars 2018 22:33, "Mark Struberg"  a écrit :
>
> folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
> include this in Tomee7 (seven!)?
> I don't think so...
>
>
> Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
> about java min version.
>
> That said agree tomee 8 can be safer for a long terms choice.
>
> LieGrue,strub
>
>
> On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
> alex.m3...@gmail.com> wrote:
>
>  Hello,
>
> To continue on this thread: I have updated
> https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
> explicit.
> New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"
>
> Could this be part of next 7.0.5-snapshot ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>>
>> Hi Romain,
>>
>> Are you suggesting that instead of waiting for TomEE 7.0.5 people
>> should upgrade to TomEE 8 ?
>>
>>
>> Yes
>>
>>
>> IHMO it's a bigger step for people : major version changes usually
>> involves major impacts (at least that's my experience).
>>
>>
>> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
>> 7. Here it should even be smoother.
>>
>> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
>> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
>> 1.1.x to get all the fixes committed so far.
>>
>>
>> +1 from me too
>>
>> After all ,Java 7 end of public updates was in April 2015, so making
>> Java 8 as the minimum prerequisite for TomEE7 three years later after
>> this date sounds very reasonable.
>>
>> Thanks,
>> Alexandre
>>
>>
>>
>>
>> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>>> Le 31 mars 2018 15:00, "Jonathan Gallimore" >
>>> a écrit :
>>>
>>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>>
>>> I'm not fussed either way, but we should discuss it and encourage input
>>> from the wider community. I'm sure I've asked before if it's ok to
> require
>>> Java 8 and still target EE 7, but I can't remember if it was definitively
>>> answered or not, and if it was, I can't remember what the answer was.
>>>
>>>
>>> Mixed thread.
>>>
>>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>>> ignore this one and upgrade straight after. Just thinking out loud.
>>>
>>>
>>> Jon
>>>
>>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>>>
 Hello,

 I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
 Johnzon 1.1.x ?

 Best regards,
 Alexandre


 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
 > We can but we miss (ATM) a looot of fixes.
 >
 > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
 jonathan.gallim...@gmail.com>
 > a écrit :
 >
 >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
 like
 >> the code is in the branch and ready to go.
 >>
 >> Jon
 >>
 >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker <
> alex.m3...@gmail.com
>>>
 >> wrote:
 >>
 >> > (sorry previous mail got truncated)
 >> >
 >> > Hello Jon,
 >> >
 >> > To answer your question about whether or not my expected Johnzon
>>> fixes
 >> > are in current "to become 

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

If we start adding EE8 features then we will further blur the line.Imo we 
should remain clean and push for TomEE8 instead...
LieGrue,strub
 

On Saturday, 31 March 2018, 23:00:43 CEST, Romain Manni-Bucau 
 wrote:  
 
 Le 31 mars 2018 22:33, "Mark Struberg"  a écrit :

folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
include this in Tomee7 (seven!)?
I don't think so...


Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
about java min version.

That said agree tomee 8 can be safer for a long terms choice.

LieGrue,strub


    On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
alex.m3...@gmail.com> wrote:

 Hello,

To continue on this thread: I have updated
https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
explicit.
New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"

Could this be part of next 7.0.5-snapshot ?

Best regards,
Alexandre


2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>
> Hi Romain,
>
> Are you suggesting that instead of waiting for TomEE 7.0.5 people
> should upgrade to TomEE 8 ?
>
>
> Yes
>
>
> IHMO it's a bigger step for people : major version changes usually
> involves major impacts (at least that's my experience).
>
>
> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
> 7. Here it should even be smoother.
>
> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
> 1.1.x to get all the fixes committed so far.
>
>
> +1 from me too
>
> After all ,Java 7 end of public updates was in April 2015, so making
> Java 8 as the minimum prerequisite for TomEE7 three years later after
> this date sounds very reasonable.
>
> Thanks,
> Alexandre
>
>
>
>
> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
>> a écrit :
>>
>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>
>> I'm not fussed either way, but we should discuss it and encourage input
>> from the wider community. I'm sure I've asked before if it's ok to
require
>> Java 8 and still target EE 7, but I can't remember if it was definitively
>> answered or not, and if it was, I can't remember what the answer was.
>>
>>
>> Mixed thread.
>>
>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>> ignore this one and upgrade straight after. Just thinking out loud.
>>
>>
>> Jon
>>
>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>>
>>> Hello,
>>>
>>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>>> Johnzon 1.1.x ?
>>>
>>> Best regards,
>>> Alexandre
>>>
>>>
>>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>>> > We can but we miss (ATM) a looot of fixes.
>>> >
>>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>>> jonathan.gallim...@gmail.com>
>>> > a écrit :
>>> >
>>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>>> like
>>> >> the code is in the branch and ready to go.
>>> >>
>>> >> Jon
>>> >>
>>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker <
alex.m3...@gmail.com
>>
>>> >> wrote:
>>> >>
>>> >> > (sorry previous mail got truncated)
>>> >> >
>>> >> > Hello Jon,
>>> >> >
>>> >> > To answer your question about whether or not my expected Johnzon
>> fixes
>>> >> > are in current "to become TomEE 7.0.5" : my view is that this is
not
>>> >> > the case:
>>> >> >  * The following JIRA is still opened :
>>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> >  * According to discussion in same thread of message, Romain
> proposed
>>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>>> >> > don't use the proper vocabulary) and I like very this proposal
given
>>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
>> been
>>> >> > internally reported on  Johnzon 1.0.0
>>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
>> Tomcat
>>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>>> >> > users a version "as secure as possible" when it'll be released.
>>> >> >
>>> >> > Of course I volunteer to run tests on any snapshot / RC on our
large
>>> >> > number of complex web apps.
>>> >> >
>>> >> > Best regards,
>>> >> > Alexandre
>>> >> >
>>> >> >
>>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>>> >> > > Hello Jon,
>>> >> > >
>>> >> > > To answer your question about whether or not my expected Johnzon
>>> fixes
>>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
>> not
>>> >> > > the case:
>>> >> > >  * The following JIRA is still opened :
>>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> > >  * 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Le 31 mars 2018 22:33, "Mark Struberg"  a écrit :

folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to
include this in Tomee7 (seven!)?
I don't think so...


Why? Doesnt prevent to be ee7 certified + we are not so only constraint is
about java min version.

That said agree tomee 8 can be safer for a long terms choice.

LieGrue,strub


On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker <
alex.m3...@gmail.com> wrote:

 Hello,

To continue on this thread: I have updated
https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
explicit.
New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"

Could this be part of next 7.0.5-snapshot ?

Best regards,
Alexandre


2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>
> Hi Romain,
>
> Are you suggesting that instead of waiting for TomEE 7.0.5 people
> should upgrade to TomEE 8 ?
>
>
> Yes
>
>
> IHMO it's a bigger step for people : major version changes usually
> involves major impacts (at least that's my experience).
>
>
> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
> 7. Here it should even be smoother.
>
> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
> 1.1.x to get all the fixes committed so far.
>
>
> +1 from me too
>
> After all ,Java 7 end of public updates was in April 2015, so making
> Java 8 as the minimum prerequisite for TomEE7 three years later after
> this date sounds very reasonable.
>
> Thanks,
> Alexandre
>
>
>
>
> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
>> a écrit :
>>
>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>
>> I'm not fussed either way, but we should discuss it and encourage input
>> from the wider community. I'm sure I've asked before if it's ok to
require
>> Java 8 and still target EE 7, but I can't remember if it was definitively
>> answered or not, and if it was, I can't remember what the answer was.
>>
>>
>> Mixed thread.
>>
>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>> ignore this one and upgrade straight after. Just thinking out loud.
>>
>>
>> Jon
>>
>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>>
>>> Hello,
>>>
>>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>>> Johnzon 1.1.x ?
>>>
>>> Best regards,
>>> Alexandre
>>>
>>>
>>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>>> > We can but we miss (ATM) a looot of fixes.
>>> >
>>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>>> jonathan.gallim...@gmail.com>
>>> > a écrit :
>>> >
>>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>>> like
>>> >> the code is in the branch and ready to go.
>>> >>
>>> >> Jon
>>> >>
>>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker <
alex.m3...@gmail.com
>>
>>> >> wrote:
>>> >>
>>> >> > (sorry previous mail got truncated)
>>> >> >
>>> >> > Hello Jon,
>>> >> >
>>> >> > To answer your question about whether or not my expected Johnzon
>> fixes
>>> >> > are in current "to become TomEE 7.0.5" : my view is that this is
not
>>> >> > the case:
>>> >> >  * The following JIRA is still opened :
>>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> >  * According to discussion in same thread of message, Romain
> proposed
>>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>>> >> > don't use the proper vocabulary) and I like very this proposal
given
>>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
>> been
>>> >> > internally reported on  Johnzon 1.0.0
>>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
>> Tomcat
>>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>>> >> > users a version "as secure as possible" when it'll be released.
>>> >> >
>>> >> > Of course I volunteer to run tests on any snapshot / RC on our
large
>>> >> > number of complex web apps.
>>> >> >
>>> >> > Best regards,
>>> >> > Alexandre
>>> >> >
>>> >> >
>>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>>> >> > > Hello Jon,
>>> >> > >
>>> >> > > To answer your question about whether or not my expected Johnzon
>>> fixes
>>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
>> not
>>> >> > > the case:
>>> >> > >  * The following JIRA is still opened :
>>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> > >  * According to discussion in same thread of message, Romain
>>> proposed
>>> >> > > to push Johnzon 1.1.x in wha
>>> >> > >
>>> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>>> >> > jonathan.gallim...@gmail.com>:
>>> >> > >> Yes, if we want to 

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

folks stop. johnzon-1.1.7 is JSON-P-1.1 which is EE8.Do we really want to 
include this in Tomee7 (seven!)?
I don't think so...
LieGrue,strub
 

On Saturday, 31 March 2018, 19:32:52 CEST, Alex The Rocker 
 wrote:  
 
 Hello,

To continue on this thread: I have updated
https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
explicit.
New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"

Could this be part of next 7.0.5-snapshot ?

Best regards,
Alexandre


2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>
> Hi Romain,
>
> Are you suggesting that instead of waiting for TomEE 7.0.5 people
> should upgrade to TomEE 8 ?
>
>
> Yes
>
>
> IHMO it's a bigger step for people : major version changes usually
> involves major impacts (at least that's my experience).
>
>
> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
> 7. Here it should even be smoother.
>
> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
> 1.1.x to get all the fixes committed so far.
>
>
> +1 from me too
>
> After all ,Java 7 end of public updates was in April 2015, so making
> Java 8 as the minimum prerequisite for TomEE7 three years later after
> this date sounds very reasonable.
>
> Thanks,
> Alexandre
>
>
>
>
> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
>> a écrit :
>>
>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>
>> I'm not fussed either way, but we should discuss it and encourage input
>> from the wider community. I'm sure I've asked before if it's ok to require
>> Java 8 and still target EE 7, but I can't remember if it was definitively
>> answered or not, and if it was, I can't remember what the answer was.
>>
>>
>> Mixed thread.
>>
>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>> ignore this one and upgrade straight after. Just thinking out loud.
>>
>>
>> Jon
>>
>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>>
>>> Hello,
>>>
>>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>>> Johnzon 1.1.x ?
>>>
>>> Best regards,
>>> Alexandre
>>>
>>>
>>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>>> > We can but we miss (ATM) a looot of fixes.
>>> >
>>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>>> jonathan.gallim...@gmail.com>
>>> > a écrit :
>>> >
>>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>>> like
>>> >> the code is in the branch and ready to go.
>>> >>
>>> >> Jon
>>> >>
>>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker >
>>> >> wrote:
>>> >>
>>> >> > (sorry previous mail got truncated)
>>> >> >
>>> >> > Hello Jon,
>>> >> >
>>> >> > To answer your question about whether or not my expected Johnzon
>> fixes
>>> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
>>> >> > the case:
>>> >> >  * The following JIRA is still opened :
>>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> >  * According to discussion in same thread of message, Romain
> proposed
>>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>>> >> > don't use the proper vocabulary) and I like very this proposal given
>>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
>> been
>>> >> > internally reported on  Johnzon 1.0.0
>>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
>> Tomcat
>>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>>> >> > users a version "as secure as possible" when it'll be released.
>>> >> >
>>> >> > Of course I volunteer to run tests on any snapshot / RC on our large
>>> >> > number of complex web apps.
>>> >> >
>>> >> > Best regards,
>>> >> > Alexandre
>>> >> >
>>> >> >
>>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>>> >> > > Hello Jon,
>>> >> > >
>>> >> > > To answer your question about whether or not my expected Johnzon
>>> fixes
>>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
>> not
>>> >> > > the case:
>>> >> > >  * The following JIRA is still opened :
>>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> > >  * According to discussion in same thread of message, Romain
>>> proposed
>>> >> > > to push Johnzon 1.1.x in wha
>>> >> > >
>>> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>>> >> > jonathan.gallim...@gmail.com>:
>>> >> > >> Yes, if we want to release now we'd need to roll that change
> back.
>>> >> > >>
>>> >> > >> Jon
>>> >> > >>
>>> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
>>> rmannibu...@gmail.com
>>> >> >
>>> >> > >> wrote:
>>> >> > >>
>>> >> > >>> Le 29 mars 

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello,

To continue on this thread: I have updated
https://issues.apache.org/jira/browse/TOMEE-2153 title to make it more
explicit.
New title of this JIRA is now "Dependency upgrade to Johnzon 1.1.7"

Could this be part of next 7.0.5-snapshot ?

Best regards,
Alexandre


2018-03-31 18:12 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :
>
> Hi Romain,
>
> Are you suggesting that instead of waiting for TomEE 7.0.5 people
> should upgrade to TomEE 8 ?
>
>
> Yes
>
>
> IHMO it's a bigger step for people : major version changes usually
> involves major impacts (at least that's my experience).
>
>
> Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
> 7. Here it should even be smoother.
>
> I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
> if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
> 1.1.x to get all the fixes committed so far.
>
>
> +1 from me too
>
> After all ,Java 7 end of public updates was in April 2015, so making
> Java 8 as the minimum prerequisite for TomEE7 three years later after
> this date sounds very reasonable.
>
> Thanks,
> Alexandre
>
>
>
>
> 2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
>> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
>> a écrit :
>>
>> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>>
>> I'm not fussed either way, but we should discuss it and encourage input
>> from the wider community. I'm sure I've asked before if it's ok to require
>> Java 8 and still target EE 7, but I can't remember if it was definitively
>> answered or not, and if it was, I can't remember what the answer was.
>>
>>
>> Mixed thread.
>>
>> Having tomee 8 released just after the 7.0.5 it can also mean you can
>> ignore this one and upgrade straight after. Just thinking out loud.
>>
>>
>> Jon
>>
>> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>>
>>> Hello,
>>>
>>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>>> Johnzon 1.1.x ?
>>>
>>> Best regards,
>>> Alexandre
>>>
>>>
>>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>>> > We can but we miss (ATM) a looot of fixes.
>>> >
>>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>>> jonathan.gallim...@gmail.com>
>>> > a écrit :
>>> >
>>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>>> like
>>> >> the code is in the branch and ready to go.
>>> >>
>>> >> Jon
>>> >>
>>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker >
>>> >> wrote:
>>> >>
>>> >> > (sorry previous mail got truncated)
>>> >> >
>>> >> > Hello Jon,
>>> >> >
>>> >> > To answer your question about whether or not my expected Johnzon
>> fixes
>>> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
>>> >> > the case:
>>> >> >  * The following JIRA is still opened :
>>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> >  * According to discussion in same thread of message, Romain
> proposed
>>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>>> >> > don't use the proper vocabulary) and I like very this proposal given
>>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
>> been
>>> >> > internally reported on  Johnzon 1.0.0
>>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
>> Tomcat
>>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>>> >> > users a version "as secure as possible" when it'll be released.
>>> >> >
>>> >> > Of course I volunteer to run tests on any snapshot / RC on our large
>>> >> > number of complex web apps.
>>> >> >
>>> >> > Best regards,
>>> >> > Alexandre
>>> >> >
>>> >> >
>>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>>> >> > > Hello Jon,
>>> >> > >
>>> >> > > To answer your question about whether or not my expected Johnzon
>>> fixes
>>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
>> not
>>> >> > > the case:
>>> >> > >  * The following JIRA is still opened :
>>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>>> >> > >  * According to discussion in same thread of message, Romain
>>> proposed
>>> >> > > to push Johnzon 1.1.x in wha
>>> >> > >
>>> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>>> >> > jonathan.gallim...@gmail.com>:
>>> >> > >> Yes, if we want to release now we'd need to roll that change
> back.
>>> >> > >>
>>> >> > >> Jon
>>> >> > >>
>>> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
>>> rmannibu...@gmail.com
>>> >> >
>>> >> > >> wrote:
>>> >> > >>
>>> >> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
>>> >> > jonathan.gallim...@gmail.com>
>>> >> > >>> a écrit :
>>> >> > >>>
>>> >> > >>> We did talk about doing a TomEE 7 release. I'm willing to be
>>> release
>>> >> > >>> manager. I have 2 questions:
>>> >> 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Le 31 mars 2018 16:36, "Alex The Rocker"  a écrit :

Hi Romain,

Are you suggesting that instead of waiting for TomEE 7.0.5 people
should upgrade to TomEE 8 ?


Yes


IHMO it's a bigger step for people : major version changes usually
involves major impacts (at least that's my experience).


Shouldnt be the case here. Tomee 1.0 to 1.5 was way more hurting than 1 to
7. Here it should even be smoother.

I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
1.1.x to get all the fixes committed so far.


+1 from me too

After all ,Java 7 end of public updates was in April 2015, so making
Java 8 as the minimum prerequisite for TomEE7 three years later after
this date sounds very reasonable.

Thanks,
Alexandre




2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
> a écrit :
>
> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>
> I'm not fussed either way, but we should discuss it and encourage input
> from the wider community. I'm sure I've asked before if it's ok to require
> Java 8 and still target EE 7, but I can't remember if it was definitively
> answered or not, and if it was, I can't remember what the answer was.
>
>
> Mixed thread.
>
> Having tomee 8 released just after the 7.0.5 it can also mean you can
> ignore this one and upgrade straight after. Just thinking out loud.
>
>
> Jon
>
> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>
>> Hello,
>>
>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>> Johnzon 1.1.x ?
>>
>> Best regards,
>> Alexandre
>>
>>
>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>> > We can but we miss (ATM) a looot of fixes.
>> >
>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>> jonathan.gallim...@gmail.com>
>> > a écrit :
>> >
>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>> like
>> >> the code is in the branch and ready to go.
>> >>
>> >> Jon
>> >>
>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
>> >> wrote:
>> >>
>> >> > (sorry previous mail got truncated)
>> >> >
>> >> > Hello Jon,
>> >> >
>> >> > To answer your question about whether or not my expected Johnzon
> fixes
>> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
>> >> > the case:
>> >> >  * The following JIRA is still opened :
>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>> >> >  * According to discussion in same thread of message, Romain
proposed
>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>> >> > don't use the proper vocabulary) and I like very this proposal given
>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
> been
>> >> > internally reported on  Johnzon 1.0.0
>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
> Tomcat
>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>> >> > users a version "as secure as possible" when it'll be released.
>> >> >
>> >> > Of course I volunteer to run tests on any snapshot / RC on our large
>> >> > number of complex web apps.
>> >> >
>> >> > Best regards,
>> >> > Alexandre
>> >> >
>> >> >
>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>> >> > > Hello Jon,
>> >> > >
>> >> > > To answer your question about whether or not my expected Johnzon
>> fixes
>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
> not
>> >> > > the case:
>> >> > >  * The following JIRA is still opened :
>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>> >> > >  * According to discussion in same thread of message, Romain
>> proposed
>> >> > > to push Johnzon 1.1.x in wha
>> >> > >
>> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>> >> > jonathan.gallim...@gmail.com>:
>> >> > >> Yes, if we want to release now we'd need to roll that change
back.
>> >> > >>
>> >> > >> Jon
>> >> > >>
>> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
>> rmannibu...@gmail.com
>> >> >
>> >> > >> wrote:
>> >> > >>
>> >> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
>> >> > jonathan.gallim...@gmail.com>
>> >> > >>> a écrit :
>> >> > >>>
>> >> > >>> We did talk about doing a TomEE 7 release. I'm willing to be
>> release
>> >> > >>> manager. I have 2 questions:
>> >> > >>>
>> >> > >>> * Does the TomEE 7 / master branch have the fix you want
already,
>> or
>> >> is
>> >> > >>> there work to do there?
>> >> > >>>
>> >> > >>> * I did upgrade xbean to a version that handles java 9 and 10,
>> and I
>> >> > also
>> >> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to
> wait
>> >> for
>> >> > >>> releases of those, or do we want to release right away?
>> >> > >>>
>> >> > >>>
>> >> > >>> Guess we want to have a single xbean version so either wait or
>> >> 

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hi Romain,

Are you suggesting that instead of waiting for TomEE 7.0.5 people
should upgrade to TomEE 8 ?

IHMO it's a bigger step for people : major version changes usually
involves major impacts (at least that's my experience).
I'm more fond of a TomEE 7.0.5 with Java 8 as the minimum prerequisite
if this allows for the replacement of Johnzon 1.0.0 by latest Johnzon
1.1.x to get all the fixes committed so far.
After all ,Java 7 end of public updates was in April 2015, so making
Java 8 as the minimum prerequisite for TomEE7 three years later after
this date sounds very reasonable.

Thanks,
Alexandre




2018-03-31 15:44 GMT+02:00 Romain Manni-Bucau :
> Le 31 mars 2018 15:00, "Jonathan Gallimore" 
> a écrit :
>
> It requires TomEE 7.x, which targets EE7, to shift to Java 8.
>
> I'm not fussed either way, but we should discuss it and encourage input
> from the wider community. I'm sure I've asked before if it's ok to require
> Java 8 and still target EE 7, but I can't remember if it was definitively
> answered or not, and if it was, I can't remember what the answer was.
>
>
> Mixed thread.
>
> Having tomee 8 released just after the 7.0.5 it can also mean you can
> ignore this one and upgrade straight after. Just thinking out loud.
>
>
> Jon
>
> On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:
>
>> Hello,
>>
>> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
>> Johnzon 1.1.x ?
>>
>> Best regards,
>> Alexandre
>>
>>
>> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
>> > We can but we miss (ATM) a looot of fixes.
>> >
>> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
>> jonathan.gallim...@gmail.com>
>> > a écrit :
>> >
>> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
>> like
>> >> the code is in the branch and ready to go.
>> >>
>> >> Jon
>> >>
>> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
>> >> wrote:
>> >>
>> >> > (sorry previous mail got truncated)
>> >> >
>> >> > Hello Jon,
>> >> >
>> >> > To answer your question about whether or not my expected Johnzon
> fixes
>> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
>> >> > the case:
>> >> >  * The following JIRA is still opened :
>> >> > https://issues.apache.org/jira/browse/TOMEE-2153
>> >> >  * According to discussion in same thread of message, Romain proposed
>> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>> >> > don't use the proper vocabulary) and I like very this proposal given
>> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
> been
>> >> > internally reported on  Johnzon 1.0.0
>> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
> Tomcat
>> >> > 8.5.x security fix level, so that we could propose to casual TomEE
>> >> > users a version "as secure as possible" when it'll be released.
>> >> >
>> >> > Of course I volunteer to run tests on any snapshot / RC on our large
>> >> > number of complex web apps.
>> >> >
>> >> > Best regards,
>> >> > Alexandre
>> >> >
>> >> >
>> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>> >> > > Hello Jon,
>> >> > >
>> >> > > To answer your question about whether or not my expected Johnzon
>> fixes
>> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
> not
>> >> > > the case:
>> >> > >  * The following JIRA is still opened :
>> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
>> >> > >  * According to discussion in same thread of message, Romain
>> proposed
>> >> > > to push Johnzon 1.1.x in wha
>> >> > >
>> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>> >> > jonathan.gallim...@gmail.com>:
>> >> > >> Yes, if we want to release now we'd need to roll that change back.
>> >> > >>
>> >> > >> Jon
>> >> > >>
>> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
>> rmannibu...@gmail.com
>> >> >
>> >> > >> wrote:
>> >> > >>
>> >> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
>> >> > jonathan.gallim...@gmail.com>
>> >> > >>> a écrit :
>> >> > >>>
>> >> > >>> We did talk about doing a TomEE 7 release. I'm willing to be
>> release
>> >> > >>> manager. I have 2 questions:
>> >> > >>>
>> >> > >>> * Does the TomEE 7 / master branch have the fix you want already,
>> or
>> >> is
>> >> > >>> there work to do there?
>> >> > >>>
>> >> > >>> * I did upgrade xbean to a version that handles java 9 and 10,
>> and I
>> >> > also
>> >> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to
> wait
>> >> for
>> >> > >>> releases of those, or do we want to release right away?
>> >> > >>>
>> >> > >>>
>> >> > >>> Guess we want to have a single xbean version so either wait or
>> >> rollback
>> >> > >>> pby.
>> >> > >>>
>> >> > >>>
>> >> > >>> Jon
>> >> > >>>
>> >> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker <
>> >> alex.m3...@gmail.com
>> >> > >
>> >> > >>> wrote:
>> >> > >>>
>> >> > 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Le 31 mars 2018 15:00, "Jonathan Gallimore" 
a écrit :

It requires TomEE 7.x, which targets EE7, to shift to Java 8.

I'm not fussed either way, but we should discuss it and encourage input
from the wider community. I'm sure I've asked before if it's ok to require
Java 8 and still target EE 7, but I can't remember if it was definitively
answered or not, and if it was, I can't remember what the answer was.


Mixed thread.

Having tomee 8 released just after the 7.0.5 it can also mean you can
ignore this one and upgrade straight after. Just thinking out loud.


Jon

On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:

> Hello,
>
> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
> Johnzon 1.1.x ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
> > We can but we miss (ATM) a looot of fixes.
> >
> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
> jonathan.gallim...@gmail.com>
> > a écrit :
> >
> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
> like
> >> the code is in the branch and ready to go.
> >>
> >> Jon
> >>
> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
> >> wrote:
> >>
> >> > (sorry previous mail got truncated)
> >> >
> >> > Hello Jon,
> >> >
> >> > To answer your question about whether or not my expected Johnzon
fixes
> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
> >> > the case:
> >> >  * The following JIRA is still opened :
> >> > https://issues.apache.org/jira/browse/TOMEE-2153
> >> >  * According to discussion in same thread of message, Romain proposed
> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
> >> > don't use the proper vocabulary) and I like very this proposal given
> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have
been
> >> > internally reported on  Johnzon 1.0.0
> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest
Tomcat
> >> > 8.5.x security fix level, so that we could propose to casual TomEE
> >> > users a version "as secure as possible" when it'll be released.
> >> >
> >> > Of course I volunteer to run tests on any snapshot / RC on our large
> >> > number of complex web apps.
> >> >
> >> > Best regards,
> >> > Alexandre
> >> >
> >> >
> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
> >> > > Hello Jon,
> >> > >
> >> > > To answer your question about whether or not my expected Johnzon
> fixes
> >> > > are in current "to become TomEE 7.0.5" : my view is that this is
not
> >> > > the case:
> >> > >  * The following JIRA is still opened :
> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
> >> > >  * According to discussion in same thread of message, Romain
> proposed
> >> > > to push Johnzon 1.1.x in wha
> >> > >
> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
> >> > jonathan.gallim...@gmail.com>:
> >> > >> Yes, if we want to release now we'd need to roll that change back.
> >> > >>
> >> > >> Jon
> >> > >>
> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
> rmannibu...@gmail.com
> >> >
> >> > >> wrote:
> >> > >>
> >> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
> >> > jonathan.gallim...@gmail.com>
> >> > >>> a écrit :
> >> > >>>
> >> > >>> We did talk about doing a TomEE 7 release. I'm willing to be
> release
> >> > >>> manager. I have 2 questions:
> >> > >>>
> >> > >>> * Does the TomEE 7 / master branch have the fix you want already,
> or
> >> is
> >> > >>> there work to do there?
> >> > >>>
> >> > >>> * I did upgrade xbean to a version that handles java 9 and 10,
> and I
> >> > also
> >> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to
wait
> >> for
> >> > >>> releases of those, or do we want to release right away?
> >> > >>>
> >> > >>>
> >> > >>> Guess we want to have a single xbean version so either wait or
> >> rollback
> >> > >>> pby.
> >> > >>>
> >> > >>>
> >> > >>> Jon
> >> > >>>
> >> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker <
> >> alex.m3...@gmail.com
> >> > >
> >> > >>> wrote:
> >> > >>>
> >> > >>> > Hello,
> >> > >>> >
> >> > >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have
> Johnzon
> >> > 1.0.0.
> >> > >>> > Is there any chance to see Romain's proposal to ise jsonp/b
> 1.1/1.0
> >> > in
> >> > >>> > tomee 7 come out anytime soon?
> >> > >>> >
> >> > >>> > Best regards,
> >> > >>> > Alexandre
> >> > >>> >
> >> > >>> >
> >> > >>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau <
> >> rmannibu...@gmail.com
> >> > >:
> >> > >>> > > @Mark: it is tracked on johnzon (
> >> > >>> > >
> >> > >>> https://issues.apache.org/jira/plugins/servlet/mobile#
> >> > issue/JOHNZON-149
> >> > >>> > ).
> >> > >>> > > There was the proposal I did months ago to just use jsonp/b
> >> > 1.1/1.0 in
> >> > >>> > > tomee 7 (doesnt prevent anything from tomee perspective if we
> >> drop
> >> > java
> >> > >>> 7
> >> > >>> 

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

It requires TomEE 7.x, which targets EE7, to shift to Java 8.

I'm not fussed either way, but we should discuss it and encourage input
from the wider community. I'm sure I've asked before if it's ok to require
Java 8 and still target EE 7, but I can't remember if it was definitively
answered or not, and if it was, I can't remember what the answer was.

Jon

On Sat, 31 Mar 2018, 12:29 Alex The Rocker,  wrote:

> Hello,
>
> I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
> Johnzon 1.1.x ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
> > We can but we miss (ATM) a looot of fixes.
> >
> > Le 30 mars 2018 23:26, "Jonathan Gallimore" <
> jonathan.gallim...@gmail.com>
> > a écrit :
> >
> >> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks
> like
> >> the code is in the branch and ready to go.
> >>
> >> Jon
> >>
> >> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
> >> wrote:
> >>
> >> > (sorry previous mail got truncated)
> >> >
> >> > Hello Jon,
> >> >
> >> > To answer your question about whether or not my expected Johnzon fixes
> >> > are in current "to become TomEE 7.0.5" : my view is that this is not
> >> > the case:
> >> >  * The following JIRA is still opened :
> >> > https://issues.apache.org/jira/browse/TOMEE-2153
> >> >  * According to discussion in same thread of message, Romain proposed
> >> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
> >> > don't use the proper vocabulary) and I like very this proposal given
> >> > the large amount of fixes in Johnzon 1.1.x versus the pile I have been
> >> > internally reported on  Johnzon 1.0.0
> >> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest Tomcat
> >> > 8.5.x security fix level, so that we could propose to casual TomEE
> >> > users a version "as secure as possible" when it'll be released.
> >> >
> >> > Of course I volunteer to run tests on any snapshot / RC on our large
> >> > number of complex web apps.
> >> >
> >> > Best regards,
> >> > Alexandre
> >> >
> >> >
> >> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
> >> > > Hello Jon,
> >> > >
> >> > > To answer your question about whether or not my expected Johnzon
> fixes
> >> > > are in current "to become TomEE 7.0.5" : my view is that this is not
> >> > > the case:
> >> > >  * The following JIRA is still opened :
> >> > > https://issues.apache.org/jira/browse/TOMEE-2153
> >> > >  * According to discussion in same thread of message, Romain
> proposed
> >> > > to push Johnzon 1.1.x in wha
> >> > >
> >> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
> >> > jonathan.gallim...@gmail.com>:
> >> > >> Yes, if we want to release now we'd need to roll that change back.
> >> > >>
> >> > >> Jon
> >> > >>
> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, <
> rmannibu...@gmail.com
> >> >
> >> > >> wrote:
> >> > >>
> >> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
> >> > jonathan.gallim...@gmail.com>
> >> > >>> a écrit :
> >> > >>>
> >> > >>> We did talk about doing a TomEE 7 release. I'm willing to be
> release
> >> > >>> manager. I have 2 questions:
> >> > >>>
> >> > >>> * Does the TomEE 7 / master branch have the fix you want already,
> or
> >> is
> >> > >>> there work to do there?
> >> > >>>
> >> > >>> * I did upgrade xbean to a version that handles java 9 and 10,
> and I
> >> > also
> >> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to wait
> >> for
> >> > >>> releases of those, or do we want to release right away?
> >> > >>>
> >> > >>>
> >> > >>> Guess we want to have a single xbean version so either wait or
> >> rollback
> >> > >>> pby.
> >> > >>>
> >> > >>>
> >> > >>> Jon
> >> > >>>
> >> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker <
> >> alex.m3...@gmail.com
> >> > >
> >> > >>> wrote:
> >> > >>>
> >> > >>> > Hello,
> >> > >>> >
> >> > >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have
> Johnzon
> >> > 1.0.0.
> >> > >>> > Is there any chance to see Romain's proposal to ise jsonp/b
> 1.1/1.0
> >> > in
> >> > >>> > tomee 7 come out anytime soon?
> >> > >>> >
> >> > >>> > Best regards,
> >> > >>> > Alexandre
> >> > >>> >
> >> > >>> >
> >> > >>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau <
> >> rmannibu...@gmail.com
> >> > >:
> >> > >>> > > @Mark: it is tracked on johnzon (
> >> > >>> > >
> >> > >>> https://issues.apache.org/jira/plugins/servlet/mobile#
> >> > issue/JOHNZON-149
> >> > >>> > ).
> >> > >>> > > There was the proposal I did months ago to just use jsonp/b
> >> > 1.1/1.0 in
> >> > >>> > > tomee 7 (doesnt prevent anything from tomee perspective if we
> >> drop
> >> > java
> >> > >>> 7
> >> > >>> > > compat). If not desired we should redo 1.x from master pby to
> >> > avoid an
> >> > >>> > half
> >> > >>> > > merged branch.
> >> > >>> > >
> >> > >>> > > Le 4 mars 2018 12:40, "Mark Struberg"
>  >> >
> >> > a

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello,

I agree with Romain : couldn't TomEE 7.0.5 be based on latest stable
Johnzon 1.1.x ?

Best regards,
Alexandre


2018-03-31 11:16 GMT+02:00 Romain Manni-Bucau :
> We can but we miss (ATM) a looot of fixes.
>
> Le 30 mars 2018 23:26, "Jonathan Gallimore" 
> a écrit :
>
>> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks like
>> the code is in the branch and ready to go.
>>
>> Jon
>>
>> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
>> wrote:
>>
>> > (sorry previous mail got truncated)
>> >
>> > Hello Jon,
>> >
>> > To answer your question about whether or not my expected Johnzon fixes
>> > are in current "to become TomEE 7.0.5" : my view is that this is not
>> > the case:
>> >  * The following JIRA is still opened :
>> > https://issues.apache.org/jira/browse/TOMEE-2153
>> >  * According to discussion in same thread of message, Romain proposed
>> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
>> > don't use the proper vocabulary) and I like very this proposal given
>> > the large amount of fixes in Johnzon 1.1.x versus the pile I have been
>> > internally reported on  Johnzon 1.0.0
>> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest Tomcat
>> > 8.5.x security fix level, so that we could propose to casual TomEE
>> > users a version "as secure as possible" when it'll be released.
>> >
>> > Of course I volunteer to run tests on any snapshot / RC on our large
>> > number of complex web apps.
>> >
>> > Best regards,
>> > Alexandre
>> >
>> >
>> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
>> > > Hello Jon,
>> > >
>> > > To answer your question about whether or not my expected Johnzon fixes
>> > > are in current "to become TomEE 7.0.5" : my view is that this is not
>> > > the case:
>> > >  * The following JIRA is still opened :
>> > > https://issues.apache.org/jira/browse/TOMEE-2153
>> > >  * According to discussion in same thread of message, Romain proposed
>> > > to push Johnzon 1.1.x in wha
>> > >
>> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
>> > jonathan.gallim...@gmail.com>:
>> > >> Yes, if we want to release now we'd need to roll that change back.
>> > >>
>> > >> Jon
>> > >>
>> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, > >
>> > >> wrote:
>> > >>
>> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
>> > jonathan.gallim...@gmail.com>
>> > >>> a écrit :
>> > >>>
>> > >>> We did talk about doing a TomEE 7 release. I'm willing to be release
>> > >>> manager. I have 2 questions:
>> > >>>
>> > >>> * Does the TomEE 7 / master branch have the fix you want already, or
>> is
>> > >>> there work to do there?
>> > >>>
>> > >>> * I did upgrade xbean to a version that handles java 9 and 10, and I
>> > also
>> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to wait
>> for
>> > >>> releases of those, or do we want to release right away?
>> > >>>
>> > >>>
>> > >>> Guess we want to have a single xbean version so either wait or
>> rollback
>> > >>> pby.
>> > >>>
>> > >>>
>> > >>> Jon
>> > >>>
>> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker <
>> alex.m3...@gmail.com
>> > >
>> > >>> wrote:
>> > >>>
>> > >>> > Hello,
>> > >>> >
>> > >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon
>> > 1.0.0.
>> > >>> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0
>> > in
>> > >>> > tomee 7 come out anytime soon?
>> > >>> >
>> > >>> > Best regards,
>> > >>> > Alexandre
>> > >>> >
>> > >>> >
>> > >>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau <
>> rmannibu...@gmail.com
>> > >:
>> > >>> > > @Mark: it is tracked on johnzon (
>> > >>> > >
>> > >>> https://issues.apache.org/jira/plugins/servlet/mobile#
>> > issue/JOHNZON-149
>> > >>> > ).
>> > >>> > > There was the proposal I did months ago to just use jsonp/b
>> > 1.1/1.0 in
>> > >>> > > tomee 7 (doesnt prevent anything from tomee perspective if we
>> drop
>> > java
>> > >>> 7
>> > >>> > > compat). If not desired we should redo 1.x from master pby to
>> > avoid an
>> > >>> > half
>> > >>> > > merged branch.
>> > >>> > >
>> > >>> > > Le 4 mars 2018 12:40, "Mark Struberg" > >
>> > a
>> > >>> > écrit :
>> > >>> > >
>> > >>> > >> Hi Alex!
>> > >>> > >>
>> > >>> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0
>> is
>> > >>> indeed
>> > >>> > >> the last version we shipped so far.
>> > >>> > >>
>> > >>> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>> > >>> > >> Those are all EE8 specs and thus this is also the version used
>> in
>> > >>> > TomEE8.
>> > >>> > >>
>> > >>> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x
>> > (EE7)
>> > >>> > then
>> > >>> > >> please identify the tickets you suggest to have fixed and report
>> > them
>> > >>> on
>> > >>> > >> the d...@johnzon.apache.org list.
>> > >>> > >> What could work is if you go 

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

We can but we miss (ATM) a looot of fixes.

Le 30 mars 2018 23:26, "Jonathan Gallimore" 
a écrit :

> I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks like
> the code is in the branch and ready to go.
>
> Jon
>
> On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
> wrote:
>
> > (sorry previous mail got truncated)
> >
> > Hello Jon,
> >
> > To answer your question about whether or not my expected Johnzon fixes
> > are in current "to become TomEE 7.0.5" : my view is that this is not
> > the case:
> >  * The following JIRA is still opened :
> > https://issues.apache.org/jira/browse/TOMEE-2153
> >  * According to discussion in same thread of message, Romain proposed
> > to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
> > don't use the proper vocabulary) and I like very this proposal given
> > the large amount of fixes in Johnzon 1.1.x versus the pile I have been
> > internally reported on  Johnzon 1.0.0
> >  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest Tomcat
> > 8.5.x security fix level, so that we could propose to casual TomEE
> > users a version "as secure as possible" when it'll be released.
> >
> > Of course I volunteer to run tests on any snapshot / RC on our large
> > number of complex web apps.
> >
> > Best regards,
> > Alexandre
> >
> >
> > 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
> > > Hello Jon,
> > >
> > > To answer your question about whether or not my expected Johnzon fixes
> > > are in current "to become TomEE 7.0.5" : my view is that this is not
> > > the case:
> > >  * The following JIRA is still opened :
> > > https://issues.apache.org/jira/browse/TOMEE-2153
> > >  * According to discussion in same thread of message, Romain proposed
> > > to push Johnzon 1.1.x in wha
> > >
> > > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>:
> > >> Yes, if we want to release now we'd need to roll that change back.
> > >>
> > >> Jon
> > >>
> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau,  >
> > >> wrote:
> > >>
> > >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
> > jonathan.gallim...@gmail.com>
> > >>> a écrit :
> > >>>
> > >>> We did talk about doing a TomEE 7 release. I'm willing to be release
> > >>> manager. I have 2 questions:
> > >>>
> > >>> * Does the TomEE 7 / master branch have the fix you want already, or
> is
> > >>> there work to do there?
> > >>>
> > >>> * I did upgrade xbean to a version that handles java 9 and 10, and I
> > also
> > >>> pushed updates to OWB and OpenJPA for the same. Do we want to wait
> for
> > >>> releases of those, or do we want to release right away?
> > >>>
> > >>>
> > >>> Guess we want to have a single xbean version so either wait or
> rollback
> > >>> pby.
> > >>>
> > >>>
> > >>> Jon
> > >>>
> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker <
> alex.m3...@gmail.com
> > >
> > >>> wrote:
> > >>>
> > >>> > Hello,
> > >>> >
> > >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon
> > 1.0.0.
> > >>> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0
> > in
> > >>> > tomee 7 come out anytime soon?
> > >>> >
> > >>> > Best regards,
> > >>> > Alexandre
> > >>> >
> > >>> >
> > >>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >>> > > @Mark: it is tracked on johnzon (
> > >>> > >
> > >>> https://issues.apache.org/jira/plugins/servlet/mobile#
> > issue/JOHNZON-149
> > >>> > ).
> > >>> > > There was the proposal I did months ago to just use jsonp/b
> > 1.1/1.0 in
> > >>> > > tomee 7 (doesnt prevent anything from tomee perspective if we
> drop
> > java
> > >>> 7
> > >>> > > compat). If not desired we should redo 1.x from master pby to
> > avoid an
> > >>> > half
> > >>> > > merged branch.
> > >>> > >
> > >>> > > Le 4 mars 2018 12:40, "Mark Struberg"  >
> > a
> > >>> > écrit :
> > >>> > >
> > >>> > >> Hi Alex!
> > >>> > >>
> > >>> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0
> is
> > >>> indeed
> > >>> > >> the last version we shipped so far.
> > >>> > >>
> > >>> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> > >>> > >> Those are all EE8 specs and thus this is also the version used
> in
> > >>> > TomEE8.
> > >>> > >>
> > >>> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x
> > (EE7)
> > >>> > then
> > >>> > >> please identify the tickets you suggest to have fixed and report
> > them
> > >>> on
> > >>> > >> the d...@johnzon.apache.org list.
> > >>> > >> What could work is if you go through either the tickets resolved
> > in
> > >>> > >> various johnzon-1.1.x versions, or scan the git log for fixes
> you
> > want
> > >>> > to
> > >>> > >> have backported.
> > >>> > >> We will then discuss it over there, create tickets and then
> merge
> > back
> > >>> > the
> > >>> > >> stuff.
> > >>> > >> The Johnzon team is surely happy 

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

I wonder if we can get a Johnzon 1.0.1 release, targetting EE7? Looks like
the code is in the branch and ready to go.

Jon

On Fri, Mar 30, 2018 at 9:03 AM, Alex The Rocker 
wrote:

> (sorry previous mail got truncated)
>
> Hello Jon,
>
> To answer your question about whether or not my expected Johnzon fixes
> are in current "to become TomEE 7.0.5" : my view is that this is not
> the case:
>  * The following JIRA is still opened :
> https://issues.apache.org/jira/browse/TOMEE-2153
>  * According to discussion in same thread of message, Romain proposed
> to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
> don't use the proper vocabulary) and I like very this proposal given
> the large amount of fixes in Johnzon 1.1.x versus the pile I have been
> internally reported on  Johnzon 1.0.0
>  * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest Tomcat
> 8.5.x security fix level, so that we could propose to casual TomEE
> users a version "as secure as possible" when it'll be released.
>
> Of course I volunteer to run tests on any snapshot / RC on our large
> number of complex web apps.
>
> Best regards,
> Alexandre
>
>
> 2018-03-30 9:59 GMT+02:00 Alex The Rocker :
> > Hello Jon,
> >
> > To answer your question about whether or not my expected Johnzon fixes
> > are in current "to become TomEE 7.0.5" : my view is that this is not
> > the case:
> >  * The following JIRA is still opened :
> > https://issues.apache.org/jira/browse/TOMEE-2153
> >  * According to discussion in same thread of message, Romain proposed
> > to push Johnzon 1.1.x in wha
> >
> > 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore <
> jonathan.gallim...@gmail.com>:
> >> Yes, if we want to release now we'd need to roll that change back.
> >>
> >> Jon
> >>
> >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, 
> >> wrote:
> >>
> >>> Le 29 mars 2018 18:23, "Jonathan Gallimore" <
> jonathan.gallim...@gmail.com>
> >>> a écrit :
> >>>
> >>> We did talk about doing a TomEE 7 release. I'm willing to be release
> >>> manager. I have 2 questions:
> >>>
> >>> * Does the TomEE 7 / master branch have the fix you want already, or is
> >>> there work to do there?
> >>>
> >>> * I did upgrade xbean to a version that handles java 9 and 10, and I
> also
> >>> pushed updates to OWB and OpenJPA for the same. Do we want to wait for
> >>> releases of those, or do we want to release right away?
> >>>
> >>>
> >>> Guess we want to have a single xbean version so either wait or rollback
> >>> pby.
> >>>
> >>>
> >>> Jon
> >>>
> >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker  >
> >>> wrote:
> >>>
> >>> > Hello,
> >>> >
> >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon
> 1.0.0.
> >>> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0
> in
> >>> > tomee 7 come out anytime soon?
> >>> >
> >>> > Best regards,
> >>> > Alexandre
> >>> >
> >>> >
> >>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau  >:
> >>> > > @Mark: it is tracked on johnzon (
> >>> > >
> >>> https://issues.apache.org/jira/plugins/servlet/mobile#
> issue/JOHNZON-149
> >>> > ).
> >>> > > There was the proposal I did months ago to just use jsonp/b
> 1.1/1.0 in
> >>> > > tomee 7 (doesnt prevent anything from tomee perspective if we drop
> java
> >>> 7
> >>> > > compat). If not desired we should redo 1.x from master pby to
> avoid an
> >>> > half
> >>> > > merged branch.
> >>> > >
> >>> > > Le 4 mars 2018 12:40, "Mark Struberg" 
> a
> >>> > écrit :
> >>> > >
> >>> > >> Hi Alex!
> >>> > >>
> >>> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
> >>> indeed
> >>> > >> the last version we shipped so far.
> >>> > >>
> >>> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> >>> > >> Those are all EE8 specs and thus this is also the version used in
> >>> > TomEE8.
> >>> > >>
> >>> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x
> (EE7)
> >>> > then
> >>> > >> please identify the tickets you suggest to have fixed and report
> them
> >>> on
> >>> > >> the d...@johnzon.apache.org list.
> >>> > >> What could work is if you go through either the tickets resolved
> in
> >>> > >> various johnzon-1.1.x versions, or scan the git log for fixes you
> want
> >>> > to
> >>> > >> have backported.
> >>> > >> We will then discuss it over there, create tickets and then merge
> back
> >>> > the
> >>> > >> stuff.
> >>> > >> The Johnzon team is surely happy about every helping hand!
> >>> > >>
> >>> > >> Btw, that's really the same for almost all the parts of TomEE.
> >>> > >> 85% of the tickets and improvements are really happening at all
> the
> >>> > other
> >>> > >> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> >>> > Geronimo,
> >>> > >> etc.
> >>> > >>
> >>> > >> Of course it's a good idea to keep the TomEE project in the loop
> from
> >>> a
> >>> > >> 

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

(sorry previous mail got truncated)

Hello Jon,

To answer your question about whether or not my expected Johnzon fixes
are in current "to become TomEE 7.0.5" : my view is that this is not
the case:
 * The following JIRA is still opened :
https://issues.apache.org/jira/browse/TOMEE-2153
 * According to discussion in same thread of message, Romain proposed
to push Johnzon 1.1.x in current TomEE 7.x repository (sorry if I
don't use the proper vocabulary) and I like very this proposal given
the large amount of fixes in Johnzon 1.1.x versus the pile I have been
internally reported on  Johnzon 1.0.0
 * Appart from Johnzon 1.1.x, TomEE 7.0.5 should include latest Tomcat
8.5.x security fix level, so that we could propose to casual TomEE
users a version "as secure as possible" when it'll be released.

Of course I volunteer to run tests on any snapshot / RC on our large
number of complex web apps.

Best regards,
Alexandre


2018-03-30 9:59 GMT+02:00 Alex The Rocker :
> Hello Jon,
>
> To answer your question about whether or not my expected Johnzon fixes
> are in current "to become TomEE 7.0.5" : my view is that this is not
> the case:
>  * The following JIRA is still opened :
> https://issues.apache.org/jira/browse/TOMEE-2153
>  * According to discussion in same thread of message, Romain proposed
> to push Johnzon 1.1.x in wha
>
> 2018-03-29 19:00 GMT+02:00 Jonathan Gallimore :
>> Yes, if we want to release now we'd need to roll that change back.
>>
>> Jon
>>
>> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, 
>> wrote:
>>
>>> Le 29 mars 2018 18:23, "Jonathan Gallimore" 
>>> a écrit :
>>>
>>> We did talk about doing a TomEE 7 release. I'm willing to be release
>>> manager. I have 2 questions:
>>>
>>> * Does the TomEE 7 / master branch have the fix you want already, or is
>>> there work to do there?
>>>
>>> * I did upgrade xbean to a version that handles java 9 and 10, and I also
>>> pushed updates to OWB and OpenJPA for the same. Do we want to wait for
>>> releases of those, or do we want to release right away?
>>>
>>>
>>> Guess we want to have a single xbean version so either wait or rollback
>>> pby.
>>>
>>>
>>> Jon
>>>
>>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker 
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon 1.0.0.
>>> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0 in
>>> > tomee 7 come out anytime soon?
>>> >
>>> > Best regards,
>>> > Alexandre
>>> >
>>> >
>>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
>>> > > @Mark: it is tracked on johnzon (
>>> > >
>>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149
>>> > ).
>>> > > There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
>>> > > tomee 7 (doesnt prevent anything from tomee perspective if we drop java
>>> 7
>>> > > compat). If not desired we should redo 1.x from master pby to avoid an
>>> > half
>>> > > merged branch.
>>> > >
>>> > > Le 4 mars 2018 12:40, "Mark Struberg"  a
>>> > écrit :
>>> > >
>>> > >> Hi Alex!
>>> > >>
>>> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
>>> indeed
>>> > >> the last version we shipped so far.
>>> > >>
>>> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>>> > >> Those are all EE8 specs and thus this is also the version used in
>>> > TomEE8.
>>> > >>
>>> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
>>> > then
>>> > >> please identify the tickets you suggest to have fixed and report them
>>> on
>>> > >> the d...@johnzon.apache.org list.
>>> > >> What could work is if you go through either the tickets resolved in
>>> > >> various johnzon-1.1.x versions, or scan the git log for fixes you want
>>> > to
>>> > >> have backported.
>>> > >> We will then discuss it over there, create tickets and then merge back
>>> > the
>>> > >> stuff.
>>> > >> The Johnzon team is surely happy about every helping hand!
>>> > >>
>>> > >> Btw, that's really the same for almost all the parts of TomEE.
>>> > >> 85% of the tickets and improvements are really happening at all the
>>> > other
>>> > >> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
>>> > Geronimo,
>>> > >> etc.
>>> > >>
>>> > >> Of course it's a good idea to keep the TomEE project in the loop from
>>> a
>>> > >> high-level perspective. For example to summarise the tickets which
>>> will
>>> > get
>>> > >> resolved.
>>> > >> But the actual work + the release etc will happen on the Johnzon, OWB,
>>> > etc
>>> > >> lists.
>>> > >>
>>> > >> txs and LieGrue,
>>> > >> strub
>>> > >>
>>> > >>
>>> > >>
>>> > >> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
>>> alex.m3...@gmail.com
>>> > >:
>>> > >> >
>>> > >> > Hello,
>>> > >> >
>>> > >> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our 

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Jon,

To answer your question about whether or not my expected Johnzon fixes
are in current "to become TomEE 7.0.5" : my view is that this is not
the case:
 * The following JIRA is still opened :
https://issues.apache.org/jira/browse/TOMEE-2153
 * According to discussion in same thread of message, Romain proposed
to push Johnzon 1.1.x in wha

2018-03-29 19:00 GMT+02:00 Jonathan Gallimore :
> Yes, if we want to release now we'd need to roll that change back.
>
> Jon
>
> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, 
> wrote:
>
>> Le 29 mars 2018 18:23, "Jonathan Gallimore" 
>> a écrit :
>>
>> We did talk about doing a TomEE 7 release. I'm willing to be release
>> manager. I have 2 questions:
>>
>> * Does the TomEE 7 / master branch have the fix you want already, or is
>> there work to do there?
>>
>> * I did upgrade xbean to a version that handles java 9 and 10, and I also
>> pushed updates to OWB and OpenJPA for the same. Do we want to wait for
>> releases of those, or do we want to release right away?
>>
>>
>> Guess we want to have a single xbean version so either wait or rollback
>> pby.
>>
>>
>> Jon
>>
>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker 
>> wrote:
>>
>> > Hello,
>> >
>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon 1.0.0.
>> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0 in
>> > tomee 7 come out anytime soon?
>> >
>> > Best regards,
>> > Alexandre
>> >
>> >
>> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
>> > > @Mark: it is tracked on johnzon (
>> > >
>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149
>> > ).
>> > > There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
>> > > tomee 7 (doesnt prevent anything from tomee perspective if we drop java
>> 7
>> > > compat). If not desired we should redo 1.x from master pby to avoid an
>> > half
>> > > merged branch.
>> > >
>> > > Le 4 mars 2018 12:40, "Mark Struberg"  a
>> > écrit :
>> > >
>> > >> Hi Alex!
>> > >>
>> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
>> indeed
>> > >> the last version we shipped so far.
>> > >>
>> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>> > >> Those are all EE8 specs and thus this is also the version used in
>> > TomEE8.
>> > >>
>> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
>> > then
>> > >> please identify the tickets you suggest to have fixed and report them
>> on
>> > >> the d...@johnzon.apache.org list.
>> > >> What could work is if you go through either the tickets resolved in
>> > >> various johnzon-1.1.x versions, or scan the git log for fixes you want
>> > to
>> > >> have backported.
>> > >> We will then discuss it over there, create tickets and then merge back
>> > the
>> > >> stuff.
>> > >> The Johnzon team is surely happy about every helping hand!
>> > >>
>> > >> Btw, that's really the same for almost all the parts of TomEE.
>> > >> 85% of the tickets and improvements are really happening at all the
>> > other
>> > >> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
>> > Geronimo,
>> > >> etc.
>> > >>
>> > >> Of course it's a good idea to keep the TomEE project in the loop from
>> a
>> > >> high-level perspective. For example to summarise the tickets which
>> will
>> > get
>> > >> resolved.
>> > >> But the actual work + the release etc will happen on the Johnzon, OWB,
>> > etc
>> > >> lists.
>> > >>
>> > >> txs and LieGrue,
>> > >> strub
>> > >>
>> > >>
>> > >>
>> > >> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
>> alex.m3...@gmail.com
>> > >:
>> > >> >
>> > >> > Hello,
>> > >> >
>> > >> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large
>> > web
>> > >> apps!
>> > >> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0
>> if
>> > >> > I remember well), could 7.0.5 embedded a decently more recent
>> Johnzon
>> > >> > version to fix the tons of issues we had to hack around with Johnzon
>> > >> > 1.0.0 ?
>> > >> >
>> > >> > Thanks,
>> > >> > Alex
>> > >> >
>> > >> > 2018-03-02 14:56 GMT+01:00 Mark Struberg > >:
>> > >> >> hi folks!
>> > >> >>
>> > >> >> We discussed this quite some times and we got good feedback so far.
>> > So
>> > >> it's finally time to make this reality.
>> > >> >>
>> > >> >> Over the weekend I'd like to switch TomEE to master and create a
>> > >> maintenance branch for Tomee7.
>> > >> >>
>> > >> >> After that I'd love to roll a first TomEE8 version in say one month
>> > >> from now.
>> > >> >>
>> > >> >> Any objection?
>> > >> >>
>> > >> >>
>> > >> >> LieGrue,
>> > >> >> strub
>> > >> >>
>> > >>
>> > >>
>> >
>>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Yes, if we want to release now we'd need to roll that change back.

Jon

On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, 
wrote:

> Le 29 mars 2018 18:23, "Jonathan Gallimore" 
> a écrit :
>
> We did talk about doing a TomEE 7 release. I'm willing to be release
> manager. I have 2 questions:
>
> * Does the TomEE 7 / master branch have the fix you want already, or is
> there work to do there?
>
> * I did upgrade xbean to a version that handles java 9 and 10, and I also
> pushed updates to OWB and OpenJPA for the same. Do we want to wait for
> releases of those, or do we want to release right away?
>
>
> Guess we want to have a single xbean version so either wait or rollback
> pby.
>
>
> Jon
>
> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker 
> wrote:
>
> > Hello,
> >
> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon 1.0.0.
> > Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0 in
> > tomee 7 come out anytime soon?
> >
> > Best regards,
> > Alexandre
> >
> >
> > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> > > @Mark: it is tracked on johnzon (
> > >
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149
> > ).
> > > There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> > > tomee 7 (doesnt prevent anything from tomee perspective if we drop java
> 7
> > > compat). If not desired we should redo 1.x from master pby to avoid an
> > half
> > > merged branch.
> > >
> > > Le 4 mars 2018 12:40, "Mark Struberg"  a
> > écrit :
> > >
> > >> Hi Alex!
> > >>
> > >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
> indeed
> > >> the last version we shipped so far.
> > >>
> > >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> > >> Those are all EE8 specs and thus this is also the version used in
> > TomEE8.
> > >>
> > >> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
> > then
> > >> please identify the tickets you suggest to have fixed and report them
> on
> > >> the d...@johnzon.apache.org list.
> > >> What could work is if you go through either the tickets resolved in
> > >> various johnzon-1.1.x versions, or scan the git log for fixes you want
> > to
> > >> have backported.
> > >> We will then discuss it over there, create tickets and then merge back
> > the
> > >> stuff.
> > >> The Johnzon team is surely happy about every helping hand!
> > >>
> > >> Btw, that's really the same for almost all the parts of TomEE.
> > >> 85% of the tickets and improvements are really happening at all the
> > other
> > >> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> > Geronimo,
> > >> etc.
> > >>
> > >> Of course it's a good idea to keep the TomEE project in the loop from
> a
> > >> high-level perspective. For example to summarise the tickets which
> will
> > get
> > >> resolved.
> > >> But the actual work + the release etc will happen on the Johnzon, OWB,
> > etc
> > >> lists.
> > >>
> > >> txs and LieGrue,
> > >> strub
> > >>
> > >>
> > >>
> > >> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
> alex.m3...@gmail.com
> > >:
> > >> >
> > >> > Hello,
> > >> >
> > >> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large
> > web
> > >> apps!
> > >> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0
> if
> > >> > I remember well), could 7.0.5 embedded a decently more recent
> Johnzon
> > >> > version to fix the tons of issues we had to hack around with Johnzon
> > >> > 1.0.0 ?
> > >> >
> > >> > Thanks,
> > >> > Alex
> > >> >
> > >> > 2018-03-02 14:56 GMT+01:00 Mark Struberg  >:
> > >> >> hi folks!
> > >> >>
> > >> >> We discussed this quite some times and we got good feedback so far.
> > So
> > >> it's finally time to make this reality.
> > >> >>
> > >> >> Over the weekend I'd like to switch TomEE to master and create a
> > >> maintenance branch for Tomee7.
> > >> >>
> > >> >> After that I'd love to roll a first TomEE8 version in say one month
> > >> from now.
> > >> >>
> > >> >> Any objection?
> > >> >>
> > >> >>
> > >> >> LieGrue,
> > >> >> strub
> > >> >>
> > >>
> > >>
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

We did talk about doing a TomEE 7 release. I'm willing to be release
manager. I have 2 questions:

* Does the TomEE 7 / master branch have the fix you want already, or is
there work to do there?

* I did upgrade xbean to a version that handles java 9 and 10, and I also
pushed updates to OWB and OpenJPA for the same. Do we want to wait for
releases of those, or do we want to release right away?

Jon

On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker 
wrote:

> Hello,
>
> I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon 1.0.0.
> Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0 in
> tomee 7 come out anytime soon?
>
> Best regards,
> Alexandre
>
>
> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> > @Mark: it is tracked on johnzon (
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149
> ).
> > There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> > tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
> > compat). If not desired we should redo 1.x from master pby to avoid an
> half
> > merged branch.
> >
> > Le 4 mars 2018 12:40, "Mark Struberg"  a
> écrit :
> >
> >> Hi Alex!
> >>
> >> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
> >> the last version we shipped so far.
> >>
> >> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> >> Those are all EE8 specs and thus this is also the version used in
> TomEE8.
> >>
> >> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
> then
> >> please identify the tickets you suggest to have fixed and report them on
> >> the d...@johnzon.apache.org list.
> >> What could work is if you go through either the tickets resolved in
> >> various johnzon-1.1.x versions, or scan the git log for fixes you want
> to
> >> have backported.
> >> We will then discuss it over there, create tickets and then merge back
> the
> >> stuff.
> >> The Johnzon team is surely happy about every helping hand!
> >>
> >> Btw, that's really the same for almost all the parts of TomEE.
> >> 85% of the tickets and improvements are really happening at all the
> other
> >> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> Geronimo,
> >> etc.
> >>
> >> Of course it's a good idea to keep the TomEE project in the loop from a
> >> high-level perspective. For example to summarise the tickets which will
> get
> >> resolved.
> >> But the actual work + the release etc will happen on the Johnzon, OWB,
> etc
> >> lists.
> >>
> >> txs and LieGrue,
> >> strub
> >>
> >>
> >>
> >> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker  >:
> >> >
> >> > Hello,
> >> >
> >> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large
> web
> >> apps!
> >> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
> >> > I remember well), could 7.0.5 embedded a decently more recent Johnzon
> >> > version to fix the tons of issues we had to hack around with Johnzon
> >> > 1.0.0 ?
> >> >
> >> > Thanks,
> >> > Alex
> >> >
> >> > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
> >> >> hi folks!
> >> >>
> >> >> We discussed this quite some times and we got good feedback so far.
> So
> >> it's finally time to make this reality.
> >> >>
> >> >> Over the weekend I'd like to switch TomEE to master and create a
> >> maintenance branch for Tomee7.
> >> >>
> >> >> After that I'd love to roll a first TomEE8 version in say one month
> >> from now.
> >> >>
> >> >> Any objection?
> >> >>
> >> >>
> >> >> LieGrue,
> >> >> strub
> >> >>
> >>
> >>
>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello,

I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have Johnzon 1.0.0.
Is there any chance to see Romain's proposal to ise jsonp/b 1.1/1.0 in
tomee 7 come out anytime soon?

Best regards,
Alexandre


2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> @Mark: it is tracked on johnzon (
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
> compat). If not desired we should redo 1.x from master pby to avoid an half
> merged branch.
>
> Le 4 mars 2018 12:40, "Mark Struberg"  a écrit :
>
>> Hi Alex!
>>
>> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
>> the last version we shipped so far.
>>
>> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>> Those are all EE8 specs and thus this is also the version used in TomEE8.
>>
>> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then
>> please identify the tickets you suggest to have fixed and report them on
>> the d...@johnzon.apache.org list.
>> What could work is if you go through either the tickets resolved in
>> various johnzon-1.1.x versions, or scan the git log for fixes you want to
>> have backported.
>> We will then discuss it over there, create tickets and then merge back the
>> stuff.
>> The Johnzon team is surely happy about every helping hand!
>>
>> Btw, that's really the same for almost all the parts of TomEE.
>> 85% of the tickets and improvements are really happening at all the other
>> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo,
>> etc.
>>
>> Of course it's a good idea to keep the TomEE project in the loop from a
>> high-level perspective. For example to summarise the tickets which will get
>> resolved.
>> But the actual work + the release etc will happen on the Johnzon, OWB, etc
>> lists.
>>
>> txs and LieGrue,
>> strub
>>
>>
>>
>> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
>> >
>> > Hello,
>> >
>> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web
>> apps!
>> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
>> > I remember well), could 7.0.5 embedded a decently more recent Johnzon
>> > version to fix the tons of issues we had to hack around with Johnzon
>> > 1.0.0 ?
>> >
>> > Thanks,
>> > Alex
>> >
>> > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
>> >> hi folks!
>> >>
>> >> We discussed this quite some times and we got good feedback so far. So
>> it's finally time to make this reality.
>> >>
>> >> Over the weekend I'd like to switch TomEE to master and create a
>> maintenance branch for Tomee7.
>> >>
>> >> After that I'd love to roll a first TomEE8 version in say one month
>> from now.
>> >>
>> >> Any objection?
>> >>
>> >>
>> >> LieGrue,
>> >> strub
>> >>
>>
>>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Hi Felipe, your issue is not linked to tomee I think


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book


2018-03-27 15:23 GMT+02:00 Felipe Jaekel :

> Hi,
>
> I'm also looking forward for this release, since a issue I'm facing with
> 7.0.4(TOMEE-2181 ) is
> fixed on 7.0.5.
>
> Thanks
>
> Em ter, 27 de mar de 2018 às 08:57, Alex The Rocker 
> escreveu:
>
> > Hello All,
> >
> > Is there any  possibility to see a TomEE 7.0.5 release anytime soon
> > with an up to date Johnzon 1.1.x in it ?
> >
> > Best regards,
> > Alexandre
> >
> >
> > 2018-03-04 15:12 GMT+01:00 Alex The Rocker :
> > > Oops my bad: please read in my previous mail that I just opened
> > JOHNZON-160:
> > >
> > https://issues.apache.org/jira/browse/JOHNZON-160?jql=
> text%20~%20%22MapperException%22
> > >
> > > Thanks,
> > > Alexandre
> > >
> > > 2018-03-04 15:08 GMT+01:00 Alex The Rocker :
> > >> Hello Romain & Mark,
> > >>
> > >> Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
> > >> Johnzon upgrade to 1.1.x in TomEE 7.0.5.
> > >>
> > >> And I just filled JOHNZON-105 with a more specific JSON-B/Mapper
> issue:
> > >>
> > https://issues.apache.org/jira/projects/JOHNZON/issues/
> JOHNZON-105?filter=allopenissues
> > >>
> > >> It would be great to have a fix for it in upcoming TomEE 7.0.5, along
> > >> with latest security updates on embedded components (Tomcat, etc..)
> > >>
> > >> I will provide feedbacks with our large & complex web apps as soon as
> > >> there's something testable as a snapshot (or I can built stuff with
> > >> Maven, but i'll need by steps to make sure I'm pointing to appropriate
> > >> repos/versions/tags)
> > >>
> > >> Best regards,
> > >> Alex
> > >>
> > >>
> > >> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau  >:
> > >>> @Mark: it is tracked on johnzon (
> > >>>
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149
> ).
> > >>> There was the proposal I did months ago to just use jsonp/b 1.1/1.0
> in
> > >>> tomee 7 (doesnt prevent anything from tomee perspective if we drop
> > java 7
> > >>> compat). If not desired we should redo 1.x from master pby to avoid
> an
> > half
> > >>> merged branch.
> > >>>
> > >>> Le 4 mars 2018 12:40, "Mark Struberg"  a
> > écrit :
> > >>>
> >  Hi Alex!
> > 
> >  johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
> > indeed
> >  the last version we shipped so far.
> > 
> >  johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> >  Those are all EE8 specs and thus this is also the version used in
> > TomEE8.
> > 
> >  If you have some urgent need/request for a fix in Johnzon-1.0.x
> (EE7)
> > then
> >  please identify the tickets you suggest to have fixed and report
> them
> > on
> >  the d...@johnzon.apache.org list.
> >  What could work is if you go through either the tickets resolved in
> >  various johnzon-1.1.x versions, or scan the git log for fixes you
> > want to
> >  have backported.
> >  We will then discuss it over there, create tickets and then merge
> > back the
> >  stuff.
> >  The Johnzon team is surely happy about every helping hand!
> > 
> >  Btw, that's really the same for almost all the parts of TomEE.
> >  85% of the tickets and improvements are really happening at all the
> > other
> >  projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> > Geronimo,
> >  etc.
> > 
> >  Of course it's a good idea to keep the TomEE project in the loop
> from
> > a
> >  high-level perspective. For example to summarise the tickets which
> > will get
> >  resolved.
> >  But the actual work + the release etc will happen on the Johnzon,
> > OWB, etc
> >  lists.
> > 
> >  txs and LieGrue,
> >  strub
> > 
> > 
> > 
> >  > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
> > alex.m3...@gmail.com>:
> >  >
> >  > Hello,
> >  >
> >  > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our
> > large web
> >  apps!
> >  > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0
> > if
> >  > I remember well), could 7.0.5 embedded a decently more recent
> > Johnzon
> >  > version to fix the tons of issues we had to hack around with
> Johnzon
> >  > 1.0.0 ?
> >  >
> >  > Thanks,
> >  > Alex
> >  >
> >  > 2018-03-02 14:56 GMT+01:00 Mark Struberg
>  > >:
> >  >> hi folks!
> >  >>
> >  >> We discussed this quite some 

Re: [DISCUSS] switching TomEE8 to master

[Felipe Jaekel]

Hi,

I'm also looking forward for this release, since a issue I'm facing with
7.0.4(TOMEE-2181 ) is
fixed on 7.0.5.

Thanks

Em ter, 27 de mar de 2018 às 08:57, Alex The Rocker 
escreveu:

> Hello All,
>
> Is there any  possibility to see a TomEE 7.0.5 release anytime soon
> with an up to date Johnzon 1.1.x in it ?
>
> Best regards,
> Alexandre
>
>
> 2018-03-04 15:12 GMT+01:00 Alex The Rocker :
> > Oops my bad: please read in my previous mail that I just opened
> JOHNZON-160:
> >
> https://issues.apache.org/jira/browse/JOHNZON-160?jql=text%20~%20%22MapperException%22
> >
> > Thanks,
> > Alexandre
> >
> > 2018-03-04 15:08 GMT+01:00 Alex The Rocker :
> >> Hello Romain & Mark,
> >>
> >> Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
> >> Johnzon upgrade to 1.1.x in TomEE 7.0.5.
> >>
> >> And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue:
> >>
> https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues
> >>
> >> It would be great to have a fix for it in upcoming TomEE 7.0.5, along
> >> with latest security updates on embedded components (Tomcat, etc..)
> >>
> >> I will provide feedbacks with our large & complex web apps as soon as
> >> there's something testable as a snapshot (or I can built stuff with
> >> Maven, but i'll need by steps to make sure I'm pointing to appropriate
> >> repos/versions/tags)
> >>
> >> Best regards,
> >> Alex
> >>
> >>
> >> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> >>> @Mark: it is tracked on johnzon (
> >>>
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
> >>> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> >>> tomee 7 (doesnt prevent anything from tomee perspective if we drop
> java 7
> >>> compat). If not desired we should redo 1.x from master pby to avoid an
> half
> >>> merged branch.
> >>>
> >>> Le 4 mars 2018 12:40, "Mark Struberg"  a
> écrit :
> >>>
>  Hi Alex!
> 
>  johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is
> indeed
>  the last version we shipped so far.
> 
>  johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>  Those are all EE8 specs and thus this is also the version used in
> TomEE8.
> 
>  If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7)
> then
>  please identify the tickets you suggest to have fixed and report them
> on
>  the d...@johnzon.apache.org list.
>  What could work is if you go through either the tickets resolved in
>  various johnzon-1.1.x versions, or scan the git log for fixes you
> want to
>  have backported.
>  We will then discuss it over there, create tickets and then merge
> back the
>  stuff.
>  The Johnzon team is surely happy about every helping hand!
> 
>  Btw, that's really the same for almost all the parts of TomEE.
>  85% of the tickets and improvements are really happening at all the
> other
>  projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat,
> Geronimo,
>  etc.
> 
>  Of course it's a good idea to keep the TomEE project in the loop from
> a
>  high-level perspective. For example to summarise the tickets which
> will get
>  resolved.
>  But the actual work + the release etc will happen on the Johnzon,
> OWB, etc
>  lists.
> 
>  txs and LieGrue,
>  strub
> 
> 
> 
>  > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <
> alex.m3...@gmail.com>:
>  >
>  > Hello,
>  >
>  > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our
> large web
>  apps!
>  > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0
> if
>  > I remember well), could 7.0.5 embedded a decently more recent
> Johnzon
>  > version to fix the tons of issues we had to hack around with Johnzon
>  > 1.0.0 ?
>  >
>  > Thanks,
>  > Alex
>  >
>  > 2018-03-02 14:56 GMT+01:00 Mark Struberg  >:
>  >> hi folks!
>  >>
>  >> We discussed this quite some times and we got good feedback so
> far. So
>  it's finally time to make this reality.
>  >>
>  >> Over the weekend I'd like to switch TomEE to master and create a
>  maintenance branch for Tomee7.
>  >>
>  >> After that I'd love to roll a first TomEE8 version in say one month
>  from now.
>  >>
>  >> Any objection?
>  >>
>  >>
>  >> LieGrue,
>  >> strub
>  >>
> 
> 
>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello All,

Is there any  possibility to see a TomEE 7.0.5 release anytime soon
with an up to date Johnzon 1.1.x in it ?

Best regards,
Alexandre


2018-03-04 15:12 GMT+01:00 Alex The Rocker :
> Oops my bad: please read in my previous mail that I just opened JOHNZON-160:
>  
> https://issues.apache.org/jira/browse/JOHNZON-160?jql=text%20~%20%22MapperException%22
>
> Thanks,
> Alexandre
>
> 2018-03-04 15:08 GMT+01:00 Alex The Rocker :
>> Hello Romain & Mark,
>>
>> Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
>> Johnzon upgrade to 1.1.x in TomEE 7.0.5.
>>
>> And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue:
>> https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues
>>
>> It would be great to have a fix for it in upcoming TomEE 7.0.5, along
>> with latest security updates on embedded components (Tomcat, etc..)
>>
>> I will provide feedbacks with our large & complex web apps as soon as
>> there's something testable as a snapshot (or I can built stuff with
>> Maven, but i'll need by steps to make sure I'm pointing to appropriate
>> repos/versions/tags)
>>
>> Best regards,
>> Alex
>>
>>
>> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
>>> @Mark: it is tracked on johnzon (
>>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
>>> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
>>> tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
>>> compat). If not desired we should redo 1.x from master pby to avoid an half
>>> merged branch.
>>>
>>> Le 4 mars 2018 12:40, "Mark Struberg"  a écrit :
>>>
 Hi Alex!

 johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
 the last version we shipped so far.

 johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
 Those are all EE8 specs and thus this is also the version used in TomEE8.

 If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then
 please identify the tickets you suggest to have fixed and report them on
 the d...@johnzon.apache.org list.
 What could work is if you go through either the tickets resolved in
 various johnzon-1.1.x versions, or scan the git log for fixes you want to
 have backported.
 We will then discuss it over there, create tickets and then merge back the
 stuff.
 The Johnzon team is surely happy about every helping hand!

 Btw, that's really the same for almost all the parts of TomEE.
 85% of the tickets and improvements are really happening at all the other
 projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo,
 etc.

 Of course it's a good idea to keep the TomEE project in the loop from a
 high-level perspective. For example to summarise the tickets which will get
 resolved.
 But the actual work + the release etc will happen on the Johnzon, OWB, etc
 lists.

 txs and LieGrue,
 strub



 > Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
 >
 > Hello,
 >
 > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web
 apps!
 > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
 > I remember well), could 7.0.5 embedded a decently more recent Johnzon
 > version to fix the tons of issues we had to hack around with Johnzon
 > 1.0.0 ?
 >
 > Thanks,
 > Alex
 >
 > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
 >> hi folks!
 >>
 >> We discussed this quite some times and we got good feedback so far. So
 it's finally time to make this reality.
 >>
 >> Over the weekend I'd like to switch TomEE to master and create a
 maintenance branch for Tomee7.
 >>
 >> After that I'd love to roll a first TomEE8 version in say one month
 from now.
 >>
 >> Any objection?
 >>
 >>
 >> LieGrue,
 >> strub
 >>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Oops my bad: please read in my previous mail that I just opened JOHNZON-160:
 
https://issues.apache.org/jira/browse/JOHNZON-160?jql=text%20~%20%22MapperException%22

Thanks,
Alexandre

2018-03-04 15:08 GMT+01:00 Alex The Rocker :
> Hello Romain & Mark,
>
> Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
> Johnzon upgrade to 1.1.x in TomEE 7.0.5.
>
> And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue:
> https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues
>
> It would be great to have a fix for it in upcoming TomEE 7.0.5, along
> with latest security updates on embedded components (Tomcat, etc..)
>
> I will provide feedbacks with our large & complex web apps as soon as
> there's something testable as a snapshot (or I can built stuff with
> Maven, but i'll need by steps to make sure I'm pointing to appropriate
> repos/versions/tags)
>
> Best regards,
> Alex
>
>
> 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
>> @Mark: it is tracked on johnzon (
>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
>> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
>> tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
>> compat). If not desired we should redo 1.x from master pby to avoid an half
>> merged branch.
>>
>> Le 4 mars 2018 12:40, "Mark Struberg"  a écrit :
>>
>>> Hi Alex!
>>>
>>> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
>>> the last version we shipped so far.
>>>
>>> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>>> Those are all EE8 specs and thus this is also the version used in TomEE8.
>>>
>>> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then
>>> please identify the tickets you suggest to have fixed and report them on
>>> the d...@johnzon.apache.org list.
>>> What could work is if you go through either the tickets resolved in
>>> various johnzon-1.1.x versions, or scan the git log for fixes you want to
>>> have backported.
>>> We will then discuss it over there, create tickets and then merge back the
>>> stuff.
>>> The Johnzon team is surely happy about every helping hand!
>>>
>>> Btw, that's really the same for almost all the parts of TomEE.
>>> 85% of the tickets and improvements are really happening at all the other
>>> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo,
>>> etc.
>>>
>>> Of course it's a good idea to keep the TomEE project in the loop from a
>>> high-level perspective. For example to summarise the tickets which will get
>>> resolved.
>>> But the actual work + the release etc will happen on the Johnzon, OWB, etc
>>> lists.
>>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>
>>> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
>>> >
>>> > Hello,
>>> >
>>> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web
>>> apps!
>>> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
>>> > I remember well), could 7.0.5 embedded a decently more recent Johnzon
>>> > version to fix the tons of issues we had to hack around with Johnzon
>>> > 1.0.0 ?
>>> >
>>> > Thanks,
>>> > Alex
>>> >
>>> > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
>>> >> hi folks!
>>> >>
>>> >> We discussed this quite some times and we got good feedback so far. So
>>> it's finally time to make this reality.
>>> >>
>>> >> Over the weekend I'd like to switch TomEE to master and create a
>>> maintenance branch for Tomee7.
>>> >>
>>> >> After that I'd love to roll a first TomEE8 version in say one month
>>> from now.
>>> >>
>>> >> Any objection?
>>> >>
>>> >>
>>> >> LieGrue,
>>> >> strub
>>> >>
>>>
>>>

Re: [DISCUSS] switching TomEE8 to master

[Alex The Rocker]

Hello Romain & Mark,

Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking
Johnzon upgrade to 1.1.x in TomEE 7.0.5.

And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue:
https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues

It would be great to have a fix for it in upcoming TomEE 7.0.5, along
with latest security updates on embedded components (Tomcat, etc..)

I will provide feedbacks with our large & complex web apps as soon as
there's something testable as a snapshot (or I can built stuff with
Maven, but i'll need by steps to make sure I'm pointing to appropriate
repos/versions/tags)

Best regards,
Alex


2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau :
> @Mark: it is tracked on johnzon (
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
> tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
> compat). If not desired we should redo 1.x from master pby to avoid an half
> merged branch.
>
> Le 4 mars 2018 12:40, "Mark Struberg"  a écrit :
>
>> Hi Alex!
>>
>> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
>> the last version we shipped so far.
>>
>> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
>> Those are all EE8 specs and thus this is also the version used in TomEE8.
>>
>> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then
>> please identify the tickets you suggest to have fixed and report them on
>> the d...@johnzon.apache.org list.
>> What could work is if you go through either the tickets resolved in
>> various johnzon-1.1.x versions, or scan the git log for fixes you want to
>> have backported.
>> We will then discuss it over there, create tickets and then merge back the
>> stuff.
>> The Johnzon team is surely happy about every helping hand!
>>
>> Btw, that's really the same for almost all the parts of TomEE.
>> 85% of the tickets and improvements are really happening at all the other
>> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo,
>> etc.
>>
>> Of course it's a good idea to keep the TomEE project in the loop from a
>> high-level perspective. For example to summarise the tickets which will get
>> resolved.
>> But the actual work + the release etc will happen on the Johnzon, OWB, etc
>> lists.
>>
>> txs and LieGrue,
>> strub
>>
>>
>>
>> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
>> >
>> > Hello,
>> >
>> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web
>> apps!
>> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
>> > I remember well), could 7.0.5 embedded a decently more recent Johnzon
>> > version to fix the tons of issues we had to hack around with Johnzon
>> > 1.0.0 ?
>> >
>> > Thanks,
>> > Alex
>> >
>> > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
>> >> hi folks!
>> >>
>> >> We discussed this quite some times and we got good feedback so far. So
>> it's finally time to make this reality.
>> >>
>> >> Over the weekend I'd like to switch TomEE to master and create a
>> maintenance branch for Tomee7.
>> >>
>> >> After that I'd love to roll a first TomEE8 version in say one month
>> from now.
>> >>
>> >> Any objection?
>> >>
>> >>
>> >> LieGrue,
>> >> strub
>> >>
>>
>>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

@Mark: it is tracked on johnzon (
https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149).
There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in
tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7
compat). If not desired we should redo 1.x from master pby to avoid an half
merged branch.

Le 4 mars 2018 12:40, "Mark Struberg"  a écrit :

> Hi Alex!
>
> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed
> the last version we shipped so far.
>
> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0.
> Those are all EE8 specs and thus this is also the version used in TomEE8.
>
> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then
> please identify the tickets you suggest to have fixed and report them on
> the d...@johnzon.apache.org list.
> What could work is if you go through either the tickets resolved in
> various johnzon-1.1.x versions, or scan the git log for fixes you want to
> have backported.
> We will then discuss it over there, create tickets and then merge back the
> stuff.
> The Johnzon team is surely happy about every helping hand!
>
> Btw, that's really the same for almost all the parts of TomEE.
> 85% of the tickets and improvements are really happening at all the other
> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo,
> etc.
>
> Of course it's a good idea to keep the TomEE project in the loop from a
> high-level perspective. For example to summarise the tickets which will get
> resolved.
> But the actual work + the release etc will happen on the Johnzon, OWB, etc
> lists.
>
> txs and LieGrue,
> strub
>
>
>
> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
> >
> > Hello,
> >
> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web
> apps!
> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
> > I remember well), could 7.0.5 embedded a decently more recent Johnzon
> > version to fix the tons of issues we had to hack around with Johnzon
> > 1.0.0 ?
> >
> > Thanks,
> > Alex
> >
> > 2018-03-02 14:56 GMT+01:00 Mark Struberg :
> >> hi folks!
> >>
> >> We discussed this quite some times and we got good feedback so far. So
> it's finally time to make this reality.
> >>
> >> Over the weekend I'd like to switch TomEE to master and create a
> maintenance branch for Tomee7.
> >>
> >> After that I'd love to roll a first TomEE8 version in say one month
> from now.
> >>
> >> Any objection?
> >>
> >>
> >> LieGrue,
> >> strub
> >>
>
>

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

Hi Alex!

johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed the 
last version we shipped so far.

johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0. 
Those are all EE8 specs and thus this is also the version used in TomEE8.

If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then 
please identify the tickets you suggest to have fixed and report them on the 
d...@johnzon.apache.org list. 
What could work is if you go through either the tickets resolved in various 
johnzon-1.1.x versions, or scan the git log for fixes you want to have 
backported.
We will then discuss it over there, create tickets and then merge back the 
stuff.
The Johnzon team is surely happy about every helping hand!

Btw, that's really the same for almost all the parts of TomEE. 
85% of the tickets and improvements are really happening at all the other 
projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo, etc. 

Of course it's a good idea to keep the TomEE project in the loop from a 
high-level perspective. For example to summarise the tickets which will get 
resolved. 
But the actual work + the release etc will happen on the Johnzon, OWB, etc 
lists. 

txs and LieGrue,
strub



> Am 03.03.2018 um 23:32 schrieb Alex The Rocker :
> 
> Hello,
> 
> +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web apps!
> By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if
> I remember well), could 7.0.5 embedded a decently more recent Johnzon
> version to fix the tons of issues we had to hack around with Johnzon
> 1.0.0 ?
> 
> Thanks,
> Alex
> 
> 2018-03-02 14:56 GMT+01:00 Mark Struberg :
>> hi folks!
>> 
>> We discussed this quite some times and we got good feedback so far. So it's 
>> finally time to make this reality.
>> 
>> Over the weekend I'd like to switch TomEE to master and create a maintenance 
>> branch for Tomee7.
>> 
>> After that I'd love to roll a first TomEE8 version in say one month from now.
>> 
>> Any objection?
>> 
>> 
>> LieGrue,
>> strub
>> 

Re: [DISCUSS] switching TomEE8 to master

[Mark Struberg]

yes +1. 

So let's try to get TomE-7.0.5 out of the door.

And then do the switch in ~2 weeks.

LieGrue,
strub


> Am 02.03.2018 um 16:58 schrieb Matthew Broadhead 
> :
> 
> +1
> 
> On 02/03/2018 15:58, Romain Manni-Bucau wrote:
>> sounds perfect for me (thanks Jon, can help to review issues if needed)
>> 
>> 
>> Romain Manni-Bucau
>> @rmannibucau  |  Blog
>>  | Old Blog
>>  | Github  
>> |
>> LinkedIn  | Book
>> 
>> 
>> 2018-03-02 15:56 GMT+01:00 Jonathan Gallimore 
>> :
>> 
>>> I'd be happy to do a 7.0.5 release next week.
>>> 
>>> Jon
>>> 
>>> On Fri, Mar 2, 2018 at 2:16 PM, Romain Manni-Bucau 
>>> wrote:
>>> 
 @Mark: was just what you said in "sync tomee8 branch" thread
 
 
 Romain Manni-Bucau
 @rmannibucau  |  Blog
  | Old Blog
  | Github  |
 LinkedIn  | Book
 
 
 2018-03-02 15:09 GMT+01:00 Andy Gumbrecht :
 
> +1
> 
> 
> 
> On 02/03/18 14:56, Mark Struberg wrote:
> 
>> hi folks!
>> 
>> We discussed this quite some times and we got good feedback so far. So
>> it's finally time to make this reality.
>> 
>> Over the weekend I'd like to switch TomEE to master and create a
>> maintenance branch for Tomee7.
>> 
>> After that I'd love to roll a first TomEE8 version in say one month
>>> from
>> now.
>> 
>> Any objection?
>> 
>> 
>> LieGrue,
>> strub
>> 
>> 
>> 
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
> https://www.tomitribe.io
> 
> 
> Ubique
> 
> 
> 

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

Awesome, thank you

On Fri, Mar 2, 2018 at 2:58 PM, Romain Manni-Bucau 
wrote:

> sounds perfect for me (thanks Jon, can help to review issues if needed)
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>
> 2018-03-02 15:56 GMT+01:00 Jonathan Gallimore <
> jonathan.gallim...@gmail.com>
> :
>
> > I'd be happy to do a 7.0.5 release next week.
> >
> > Jon
> >
> > On Fri, Mar 2, 2018 at 2:16 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > @Mark: was just what you said in "sync tomee8 branch" thread
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github  > > rmannibucau> |
> > > LinkedIn  | Book
> > >  > > ee-8-high-performance>
> > >
> > > 2018-03-02 15:09 GMT+01:00 Andy Gumbrecht :
> > >
> > > > +1
> > > >
> > > >
> > > >
> > > > On 02/03/18 14:56, Mark Struberg wrote:
> > > >
> > > >> hi folks!
> > > >>
> > > >> We discussed this quite some times and we got good feedback so far.
> So
> > > >> it's finally time to make this reality.
> > > >>
> > > >> Over the weekend I'd like to switch TomEE to master and create a
> > > >> maintenance branch for Tomee7.
> > > >>
> > > >> After that I'd love to roll a first TomEE8 version in say one month
> > from
> > > >> now.
> > > >>
> > > >> Any objection?
> > > >>
> > > >>
> > > >> LieGrue,
> > > >> strub
> > > >>
> > > >>
> > > >>
> > > > --
> > > > Andy Gumbrecht
> > > > https://twitter.com/AndyGeeDe
> > > > http://www.tomitribe.com
> > > > https://www.tomitribe.io
> > > >
> > > >
> > > > Ubique
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

sounds perfect for me (thanks Jon, can help to review issues if needed)


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book


2018-03-02 15:56 GMT+01:00 Jonathan Gallimore 
:

> I'd be happy to do a 7.0.5 release next week.
>
> Jon
>
> On Fri, Mar 2, 2018 at 2:16 PM, Romain Manni-Bucau 
> wrote:
>
> > @Mark: was just what you said in "sync tomee8 branch" thread
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github  > rmannibucau> |
> > LinkedIn  | Book
> >  > ee-8-high-performance>
> >
> > 2018-03-02 15:09 GMT+01:00 Andy Gumbrecht :
> >
> > > +1
> > >
> > >
> > >
> > > On 02/03/18 14:56, Mark Struberg wrote:
> > >
> > >> hi folks!
> > >>
> > >> We discussed this quite some times and we got good feedback so far. So
> > >> it's finally time to make this reality.
> > >>
> > >> Over the weekend I'd like to switch TomEE to master and create a
> > >> maintenance branch for Tomee7.
> > >>
> > >> After that I'd love to roll a first TomEE8 version in say one month
> from
> > >> now.
> > >>
> > >> Any objection?
> > >>
> > >>
> > >> LieGrue,
> > >> strub
> > >>
> > >>
> > >>
> > > --
> > > Andy Gumbrecht
> > > https://twitter.com/AndyGeeDe
> > > http://www.tomitribe.com
> > > https://www.tomitribe.io
> > >
> > >
> > > Ubique
> > >
> > >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Jonathan Gallimore]

I'd be happy to do a 7.0.5 release next week.

Jon

On Fri, Mar 2, 2018 at 2:16 PM, Romain Manni-Bucau 
wrote:

> @Mark: was just what you said in "sync tomee8 branch" thread
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>
> 2018-03-02 15:09 GMT+01:00 Andy Gumbrecht :
>
> > +1
> >
> >
> >
> > On 02/03/18 14:56, Mark Struberg wrote:
> >
> >> hi folks!
> >>
> >> We discussed this quite some times and we got good feedback so far. So
> >> it's finally time to make this reality.
> >>
> >> Over the weekend I'd like to switch TomEE to master and create a
> >> maintenance branch for Tomee7.
> >>
> >> After that I'd love to roll a first TomEE8 version in say one month from
> >> now.
> >>
> >> Any objection?
> >>
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> > --
> > Andy Gumbrecht
> > https://twitter.com/AndyGeeDe
> > http://www.tomitribe.com
> > https://www.tomitribe.io
> >
> >
> > Ubique
> >
> >
>

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

@Mark: was just what you said in "sync tomee8 branch" thread


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book


2018-03-02 15:09 GMT+01:00 Andy Gumbrecht :

> +1
>
>
>
> On 02/03/18 14:56, Mark Struberg wrote:
>
>> hi folks!
>>
>> We discussed this quite some times and we got good feedback so far. So
>> it's finally time to make this reality.
>>
>> Over the weekend I'd like to switch TomEE to master and create a
>> maintenance branch for Tomee7.
>>
>> After that I'd love to roll a first TomEE8 version in say one month from
>> now.
>>
>> Any objection?
>>
>>
>> LieGrue,
>> strub
>>
>>
>>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
> https://www.tomitribe.io
>
>
> Ubique
>
>

Re: [DISCUSS] switching TomEE8 to master

[Andy Gumbrecht]

+1


On 02/03/18 14:56, Mark Struberg wrote:

hi folks!

We discussed this quite some times and we got good feedback so far. So it's 
finally time to make this reality.

Over the weekend I'd like to switch TomEE to master and create a maintenance 
branch for Tomee7.

After that I'd love to roll a first TomEE8 version in say one month from now.

Any objection?


LieGrue,
strub




--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
https://www.tomitribe.io


Ubique

Re: [DISCUSS] switching TomEE8 to master

[Romain Manni-Bucau]

Did we plan to do the 7.0.5 then switch? +1 for this, +0 to switch before
(for that reason)


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book


2018-03-02 14:56 GMT+01:00 Mark Struberg :

> hi folks!
>
> We discussed this quite some times and we got good feedback so far. So
> it's finally time to make this reality.
>
> Over the weekend I'd like to switch TomEE to master and create a
> maintenance branch for Tomee7.
>
> After that I'd love to roll a first TomEE8 version in say one month from
> now.
>
> Any objection?
>
>
> LieGrue,
> strub
>
>

[DISCUSS] switching TomEE8 to master

[Mark Struberg]

hi folks!

We discussed this quite some times and we got good feedback so far. So it's 
finally time to make this reality.

Over the weekend I'd like to switch TomEE to master and create a maintenance 
branch for Tomee7.

After that I'd love to roll a first TomEE8 version in say one month from now.

Any objection?


LieGrue,
strub