Re: [DISCUSS] switching TomEE8 to master
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 The Rocker < > alex.m3...@gmail.com >>> >> wrote: >> >> > (sorry previous mail got truncated) >> > >> > Hello Jon, >> > >> > To answer your question about wh
Re: [DISCUSS] switching TomEE8 to master
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 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 thre
Re: [DISCUSS] switching TomEE8 to master
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 >>> >> > > * 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>: >>>
Re: [DISCUSS] switching TomEE8 to master
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 release now we'd need to roll that change > back. >>> >> > >> >>> >> > >> Jon >>> >> > >> >>> >> > >> On Thu, 29 Mar 2018, 17:55 Romain Manni-Bucau, < >>> rmannibu...@gmail.com >>> >> > >>> >> >
Re: [DISCUSS] switching TomEE8 to master
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 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 >>> >> > >>> ma
Re: [DISCUSS] switching TomEE8 to master
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: >>> >> > >>> >>> >> > >>> * Does the TomEE 7 / master branch have the fix you want > already, >>> or >>> >> is >>> >> > >>> there work to do there? >>> >> > >>> >>> >> > >>> * I did upgrade xbean
Re: [DISCUSS] switching TomEE8 to master
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 >> >> rollback >> >> > >>> pby. >> >> > >>> >> >> > >>> >> >> > >>> Jon >> >> > >>> >> >> > >>> On Thu, Mar 29, 2018 at 4:16 PM, Alex The Rocker < >> >> alex.m3...@gmail.com
Re: [DISCUSS] switching TomEE8 to master
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: >> >> > >>> >> >> > >>> > Hello, >> >> > >>> > >> >> > >>> > I noticed that in latest TomEE 7.0.5 SNAPSHOT we will have >> Johnzon >> >> > 1.0.0. >> >> > >>> > Is
Re: [DISCUSS] switching TomEE8 to master
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 > >> > >>> > > compat). If not desired we should redo 1.x from master pby to > >> > avoid an > >> > >>> > half > >> > >>> > > merge
Re: [DISCUSS] switching TomEE8 to master
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 > >> > >>> > écrit : > >> > >>> > > > >> > >>> > >> Hi Alex! > >> > >>> > >> > >> > >>> > >> johnzon-1.0.x is targett
Re: [DISCUSS] switching TomEE8 to master
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 through either the tickets resolved >> > in >> > >>> > >> various johnzon-1.1.x versions, or scan the git log for fixes >> you >> > want >> > >>> > to >> >
Re: [DISCUSS] switching TomEE8 to master
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 about every helping hand! > > >>> > >> > > >>> > >> Btw, that's really the same for almost all the parts of TomEE. > > >>> > >
Re: [VOTE] Explore creating a reusable JWT Library
Le 30 mars 2018 23:46, "David Blevins" a écrit : > On Mar 29, 2018, at 10:06 PM, Romain Manni-Bucau wrote: > > Le 30 mars 2018 04:30, "David Blevins" a écrit : > > >> On Mar 29, 2018, at 12:57 PM, David Blevins > wrote: >> >>> On Mar 29, 2018, at 12:15 PM, Romain Manni-Bucau > wrote: >>> >>> Le 29 mars 2018 20:49, "David Blevins" a écrit > : >>> >>> On Mar 28, 2018, at 8:53 PM, Romain Manni-Bucau >>> wrote: > On Mar 28, 2018, at 6:29 PM, David Blevins >>> wrote: > Is your -1 on the basis that the code must be moved to Geronimo? That + the fact tomee is not and shouldnt become a put it all project > just become of scm perms IMO but stay an integration project to keep sense > and not mess up its own image and mess up the quality of our reusable libs. >>> Do you see this as a one-time situation or do you intend to vote the > same way on any future MicroProfile implementation work in TomEE? For example, should work be started to implement MicroProfile > OpenTracing in TomEE, would that PR be -1 on the basis the implementation should be > in Geronimo? >>> >>> Being said it will be in G anyway since that is half of G definition > since >>> some months now (since server has been dropped), I ll do my best to keep > it >>> consistent in our small ecosystem and do the same to have strong reusable >>> libs since there is no technical blockers @MP to have it and a strong >>> integration solution (tomee) and not a mess with an in between state. >> >> I'm reading that as a yes that you would -1 future MP implementation work > in TomEE on the basis it should live in Geronimo, but you hope it doesn't > come to that and will do your best to create good implementations in > Geronimo so it isn't necessary. >> >> If I misunderstood, please clarify. > >> On Mar 29, 2018, at 1:49 PM, Romain Manni-Bucau > wrote: >> >> Globally that is it. You explained a lot why geronimo failed and not sure >> why tomee is kind of taking the same path - well actually cause of "perms >> lack" fear from what I read. This is not a safe reason (+not that relevant >> @asf thanks to the meritocracy) and Id prefer to keep "us" being unite as >> we have been 7 years ago instead of just going on different paths cause of >> a fears. > > > I think we should openly discuss your perspective and how it might be > > perceived by the project. There are 11 +1 votes, 5 of them binding. It > > does appear that overall the project would like to move forward with the > > code. You -1 the code on the basis that it should go to Geronimo instead > > with the clear statement you will continue to -1 on future MicroProfile > > code. Can you see how this creates a situation where 11 people feel they > > have no ability to contribute to the project now or in the future? Do you > > feel this is the spirit of the Apache Way and represents community over > > code? > > > More than never but I just dont ignore other projects. I understand most of > voting people are not involved in G and therefore I can see where they come > from (and no Jon, this was not directed to you in particular). > > The main difference is Im thinking of communities and not community. I think it would be fair to assume everyone is thinking of communities plural and that no one is ignoring the greater good of Apache. Only that there are differences in opinion on what that is and how it should be achieved. > You are also plain wrong saying there is no way to contribute, there are > plenty as on any asf projects and for most people it will be the exact same. > > Project is created @G, if T duplicates it what does happen? We get an half > baked flavor on one side and another one on the other? Do you think it is > the right thing for asf David? Do you want to split communities? Do you > want to make of TomEE a put it all project which means getting rid of TomEE > as a thing? We need to acknowledge that the community voted on where to continue working on the code and that vote was overwhelmingly to continue evolving it here. The perspective of "TomEE is duplicating Geronimo" is a bit skewed as you created that repo in Geronimo during this vote. One could question if that is healthy behavior, but ultimately it's ok. Per ASF rules, duplication is absolutely ok, not a bad thing and business as usual. You feel it is bad and are entitled to that opinion, but I don't see you acknowledging your role in actively creating this duplication you don't like. There is also no code in the Geronimo repo you created, so if duplication is a concern it can be avoided. It stands to reason that for you where the code lives, Geronimo, is the most important thing and if that means duplication, that's a sacrifice you're willing to make. Again, this is an absolutely fine perspective and ok by Apache rules. People should be allowed to work where they want. There is no code cause the fact to have started 2 threads in 2 communities for the sam
