[OPTIONS] Java 11 and Java JDK origin

[Jacques Le Roux]

Hi,

During discussions in the "Oracle Java release model changes and consequences for the project" thread, we created "Upgrade OFBiz to use Java JDK
Version 11" aka OFBIZ-10757.

There we began to discuss not only if we should switch to Java 11 LTS (Long Time Support), which is obviously the best current choice, but also which
Java JDK origin we should use OOTB.

So we have few options and we should clarify what the community wants.

Options are:

 1. Do we agree to use https://adoptopenjdk.net/releases.html as Java JDK origin OOTB?
 2. Which branches should switch to Java1? Obviously the trunk and R18 should. Should R17, which is not yet released, switch also?

I hope we don't need a vote and will quickly find a consensus.

Thanks

Jacques

[taher]

Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
switch to java 11 on openjdk. This might provide stability expected by
users as indicated by Michael.

On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
<[hidden email]> wrote:

>
> Hi,
>
> During discussions in the "Oracle Java release model changes and consequences for the project" thread, we created "Upgrade OFBiz to use Java JDK
> Version 11" aka OFBIZ-10757.
>
> There we began to discuss not only if we should switch to Java 11 LTS (Long Time Support), which is obviously the best current choice, but also which
> Java JDK origin we should use OOTB.
>
> So we have few options and we should clarify what the community wants.
>
> Options are:
>
>  1. Do we agree to use https://adoptopenjdk.net/releases.html as Java JDK origin OOTB?
>  2. Which branches should switch to Java1? Obviously the trunk and R18 should. Should R17, which is not yet released, switch also?
>
> I hope we don't need a vote and will quickly find a consensus.
>
> Thanks
>
> Jacques
>

[Michael Brohl-3]

+1 for Taher's suggestion.

Thanks, Michael

Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:

> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
> switch to java 11 on openjdk. This might provide stability expected by
> users as indicated by Michael.
>
> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
> <[hidden email]> wrote:
>> Hi,
>>
>> During discussions in the "Oracle Java release model changes and consequences for the project" thread, we created "Upgrade OFBiz to use Java JDK
>> Version 11" aka OFBIZ-10757.
>>
>> There we began to discuss not only if we should switch to Java 11 LTS (Long Time Support), which is obviously the best current choice, but also which
>> Java JDK origin we should use OOTB.
>>
>> So we have few options and we should clarify what the community wants.
>>
>> Options are:
>>
>>   1. Do we agree to use https://adoptopenjdk.net/releases.html as Java JDK origin OOTB?
>>   2. Which branches should switch to Java1? Obviously the trunk and R18 should. Should R17, which is not yet released, switch also?
>>
>> I hope we don't need a vote and will quickly find a consensus.
>>
>> Thanks
>>
>> Jacques
>>

[Jacques Le Roux]

We should then make clear to our users that they will need to switch to OpenJDK if they want free security support.

I guess most are aware, but maybe not small companies or single users.

Jacques

Le 28/02/2019 à 18:48, Michael Brohl a écrit :

> +1 for Taher's suggestion.
>
> Thanks, Michael
>
> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>> switch to java 11 on openjdk. This might provide stability expected by
>> users as indicated by Michael.
>>
>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>> <[hidden email]> wrote:
>>> Hi,
>>>
>>> During discussions in the "Oracle Java release model changes and consequences for the project" thread, we created "Upgrade OFBiz to use Java JDK
>>> Version 11" aka OFBIZ-10757.
>>>
>>> There we began to discuss not only if we should switch to Java 11 LTS (Long Time Support), which is obviously the best current choice, but also which
>>> Java JDK origin we should use OOTB.
>>>
>>> So we have few options and we should clarify what the community wants.
>>>
>>> Options are:
>>>
>>>   1. Do we agree to use https://adoptopenjdk.net/releases.html as Java JDK origin OOTB?
>>>   2. Which branches should switch to Java1? Obviously the trunk and R18 should. Should R17, which is not yet released, switch also?
>>>
>>> I hope we don't need a vote and will quickly find a consensus.
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>

[Jacopo Cappellato-5]

I think that the simplest way to convey this message is to edit the README
document with a link to OpenJDK rather than Oracle JDK.

Jacopo

On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
[hidden email]> wrote:

> We should then make clear to our users that they will need to switch to
> OpenJDK if they want free security support.
>
> I guess most are aware, but maybe not small companies or single users.
>
> Jacques
>
> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
> > +1 for Taher's suggestion.
> >
> > Thanks, Michael
> >
> > Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
> >> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
> >> switch to java 11 on openjdk. This might provide stability expected by
> >> users as indicated by Michael.
> >>
> >> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
> >> <[hidden email]> wrote:
> >>> Hi,
> >>>
> >>> During discussions in the "Oracle Java release model changes and
> consequences for the project" thread, we created "Upgrade OFBiz to use Java
> JDK
> >>> Version 11" aka OFBIZ-10757.
> >>>
> >>> There we began to discuss not only if we should switch to Java 11 LTS
> (Long Time Support), which is obviously the best current choice, but also
> which
> >>> Java JDK origin we should use OOTB.
> >>>
> >>> So we have few options and we should clarify what the community wants.
> >>>
> >>> Options are:
> >>>
> >>>   1. Do we agree to use https://adoptopenjdk.net/releases.html as
> Java JDK origin OOTB?
> >>>   2. Which branches should switch to Java1? Obviously the trunk and
> R18 should. Should R17, which is not yet released, switch also?
> >>>
> >>> I hope we don't need a vote and will quickly find a consensus.
> >>>
> >>> Thanks
> >>>
> >>> Jacques
> >>>
> >
>

[Jacques Le Roux]

+1

Jacques

Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :

> I think that the simplest way to convey this message is to edit the README
> document with a link to OpenJDK rather than Oracle JDK.
>
> Jacopo
>
> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
> [hidden email]> wrote:
>
>> We should then make clear to our users that they will need to switch to
>> OpenJDK if they want free security support.
>>
>> I guess most are aware, but maybe not small companies or single users.
>>
>> Jacques
>>
>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
>>> +1 for Taher's suggestion.
>>>
>>> Thanks, Michael
>>>
>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>>>> switch to java 11 on openjdk. This might provide stability expected by
>>>> users as indicated by Michael.
>>>>
>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>>>> <[hidden email]> wrote:
>>>>> Hi,
>>>>>
>>>>> During discussions in the "Oracle Java release model changes and
>> consequences for the project" thread, we created "Upgrade OFBiz to use Java
>> JDK
>>>>> Version 11" aka OFBIZ-10757.
>>>>>
>>>>> There we began to discuss not only if we should switch to Java 11 LTS
>> (Long Time Support), which is obviously the best current choice, but also
>> which
>>>>> Java JDK origin we should use OOTB.
>>>>>
>>>>> So we have few options and we should clarify what the community wants.
>>>>>
>>>>> Options are:
>>>>>
>>>>>    1. Do we agree to use https://adoptopenjdk.net/releases.html as
>> Java JDK origin OOTB?
>>>>>    2. Which branches should switch to Java1? Obviously the trunk and
>> R18 should. Should R17, which is not yet released, switch also?
>>>>> I hope we don't need a vote and will quickly find a consensus.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Jacques
>>>>>

[Jacques Le Roux]

Maybe adding a link to https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244 would help also

Le 04/03/2019 à 12:31, Jacques Le Roux a écrit :

> +1
>
> Jacques
>
> Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :
>> I think that the simplest way to convey this message is to edit the README
>> document with a link to OpenJDK rather than Oracle JDK.
>>
>> Jacopo
>>
>> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> We should then make clear to our users that they will need to switch to
>>> OpenJDK if they want free security support.
>>>
>>> I guess most are aware, but maybe not small companies or single users.
>>>
>>> Jacques
>>>
>>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
>>>> +1 for Taher's suggestion.
>>>>
>>>> Thanks, Michael
>>>>
>>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>>>>> switch to java 11 on openjdk. This might provide stability expected by
>>>>> users as indicated by Michael.
>>>>>
>>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>>>>> <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> During discussions in the "Oracle Java release model changes and
>>> consequences for the project" thread, we created "Upgrade OFBiz to use Java
>>> JDK
>>>>>> Version 11" aka OFBIZ-10757.
>>>>>>
>>>>>> There we began to discuss not only if we should switch to Java 11 LTS
>>> (Long Time Support), which is obviously the best current choice, but also
>>> which
>>>>>> Java JDK origin we should use OOTB.
>>>>>>
>>>>>> So we have few options and we should clarify what the community wants.
>>>>>>
>>>>>> Options are:
>>>>>>
>>>>>>    1. Do we agree to use https://adoptopenjdk.net/releases.html as
>>> Java JDK origin OOTB?
>>>>>>    2. Which branches should switch to Java1? Obviously the trunk and
>>> R18 should. Should R17, which is not yet released, switch also?
>>>>>> I hope we don't need a vote and will quickly find a consensus.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Jacques
>>>>>>
>

[Nicolas Malin-2]

I agree with all proposal that make sens :)

Nicolas

On 04/03/2019 12:31, Jacques Le Roux wrote:

> +1
>
> Jacques
>
> Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :
>> I think that the simplest way to convey this message is to edit the
>> README
>> document with a link to OpenJDK rather than Oracle JDK.
>>
>> Jacopo
>>
>> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> We should then make clear to our users that they will need to switch to
>>> OpenJDK if they want free security support.
>>>
>>> I guess most are aware, but maybe not small companies or single users.
>>>
>>> Jacques
>>>
>>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
>>>> +1 for Taher's suggestion.
>>>>
>>>> Thanks, Michael
>>>>
>>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>>>>> switch to java 11 on openjdk. This might provide stability
>>>>> expected by
>>>>> users as indicated by Michael.
>>>>>
>>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>>>>> <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> During discussions in the "Oracle Java release model changes and
>>> consequences for the project" thread, we created "Upgrade OFBiz to
>>> use Java
>>> JDK
>>>>>> Version 11" aka OFBIZ-10757.
>>>>>>
>>>>>> There we began to discuss not only if we should switch to Java 11
>>>>>> LTS
>>> (Long Time Support), which is obviously the best current choice, but
>>> also
>>> which
>>>>>> Java JDK origin we should use OOTB.
>>>>>>
>>>>>> So we have few options and we should clarify what the community
>>>>>> wants.
>>>>>>
>>>>>> Options are:
>>>>>>
>>>>>>    1. Do we agree to use https://adoptopenjdk.net/releases.html as
>>> Java JDK origin OOTB?
>>>>>>    2. Which branches should switch to Java1? Obviously the trunk and
>>> R18 should. Should R17, which is not yet released, switch also?
>>>>>> I hope we don't need a vote and will quickly find a consensus.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Jacques
>>>>>>
>

[Jacques Le Roux]

Hi All,

This is now done. When should we switch the trunk and R18 to Java 11?

Thanks

Jacques

Le 05/03/2019 à 17:53, Nicolas Malin a écrit :

> I agree with all proposal that make sens :)
>
> Nicolas
>
> On 04/03/2019 12:31, Jacques Le Roux wrote:
>> +1
>>
>> Jacques
>>
>> Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :
>>> I think that the simplest way to convey this message is to edit the README
>>> document with a link to OpenJDK rather than Oracle JDK.
>>>
>>> Jacopo
>>>
>>> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>>> We should then make clear to our users that they will need to switch to
>>>> OpenJDK if they want free security support.
>>>>
>>>> I guess most are aware, but maybe not small companies or single users.
>>>>
>>>> Jacques
>>>>
>>>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
>>>>> +1 for Taher's suggestion.
>>>>>
>>>>> Thanks, Michael
>>>>>
>>>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>>>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>>>>>> switch to java 11 on openjdk. This might provide stability expected by
>>>>>> users as indicated by Michael.
>>>>>>
>>>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>>>>>> <[hidden email]> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> During discussions in the "Oracle Java release model changes and
>>>> consequences for the project" thread, we created "Upgrade OFBiz to use Java
>>>> JDK
>>>>>>> Version 11" aka OFBIZ-10757.
>>>>>>>
>>>>>>> There we began to discuss not only if we should switch to Java 11 LTS
>>>> (Long Time Support), which is obviously the best current choice, but also
>>>> which
>>>>>>> Java JDK origin we should use OOTB.
>>>>>>>
>>>>>>> So we have few options and we should clarify what the community wants.
>>>>>>>
>>>>>>> Options are:
>>>>>>>
>>>>>>>    1. Do we agree to use https://adoptopenjdk.net/releases.html as
>>>> Java JDK origin OOTB?
>>>>>>>    2. Which branches should switch to Java1? Obviously the trunk and
>>>> R18 should. Should R17, which is not yet released, switch also?
>>>>>>> I hope we don't need a vote and will quickly find a consensus.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>
>

[taher]

I would suggest to make the move as soon as ready. This includes a
final patch and an update of README

On Fri, Apr 12, 2019 at 3:28 PM Jacques Le Roux
<[hidden email]> wrote:

>
> Hi All,
>
> This is now done. When should we switch the trunk and R18 to Java 11?
>
> Thanks
>
> Jacques
>
> Le 05/03/2019 à 17:53, Nicolas Malin a écrit :
> > I agree with all proposal that make sens :)
> >
> > Nicolas
> >
> > On 04/03/2019 12:31, Jacques Le Roux wrote:
> >> +1
> >>
> >> Jacques
> >>
> >> Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :
> >>> I think that the simplest way to convey this message is to edit the README
> >>> document with a link to OpenJDK rather than Oracle JDK.
> >>>
> >>> Jacopo
> >>>
> >>> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
> >>> [hidden email]> wrote:
> >>>
> >>>> We should then make clear to our users that they will need to switch to
> >>>> OpenJDK if they want free security support.
> >>>>
> >>>> I guess most are aware, but maybe not small companies or single users.
> >>>>
> >>>> Jacques
> >>>>
> >>>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
> >>>>> +1 for Taher's suggestion.
> >>>>>
> >>>>> Thanks, Michael
> >>>>>
> >>>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
> >>>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
> >>>>>> switch to java 11 on openjdk. This might provide stability expected by
> >>>>>> users as indicated by Michael.
> >>>>>>
> >>>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
> >>>>>> <[hidden email]> wrote:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> During discussions in the "Oracle Java release model changes and
> >>>> consequences for the project" thread, we created "Upgrade OFBiz to use Java
> >>>> JDK
> >>>>>>> Version 11" aka OFBIZ-10757.
> >>>>>>>
> >>>>>>> There we began to discuss not only if we should switch to Java 11 LTS
> >>>> (Long Time Support), which is obviously the best current choice, but also
> >>>> which
> >>>>>>> Java JDK origin we should use OOTB.
> >>>>>>>
> >>>>>>> So we have few options and we should clarify what the community wants.
> >>>>>>>
> >>>>>>> Options are:
> >>>>>>>
> >>>>>>>    1. Do we agree to use https://adoptopenjdk.net/releases.html as
> >>>> Java JDK origin OOTB?
> >>>>>>>    2. Which branches should switch to Java1? Obviously the trunk and
> >>>> R18 should. Should R17, which is not yet released, switch also?
> >>>>>>> I hope we don't need a vote and will quickly find a consensus.
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>> Jacques
> >>>>>>>
> >>
> >

[Jacques Le Roux]

Since I did the update of the README files at r1857381, I believe we simply need to switch R18 and trunk to Java 11 and tackle the 18 remaining warnings

For instance we need to handle https://issues.apache.org/jira/browse/OFBIZ-6747 which is 12 warnings.

I just tested, without surprise the trunk HEAD works with Java 11

Jacques

Le 13/04/2019 à 00:20, Taher Alkhateeb a écrit :

> I would suggest to make the move as soon as ready. This includes a
> final patch and an update of README
>
> On Fri, Apr 12, 2019 at 3:28 PM Jacques Le Roux
> <[hidden email]> wrote:
>> Hi All,
>>
>> This is now done. When should we switch the trunk and R18 to Java 11?
>>
>> Thanks
>>
>> Jacques
>>
>> Le 05/03/2019 à 17:53, Nicolas Malin a écrit :
>>> I agree with all proposal that make sens :)
>>>
>>> Nicolas
>>>
>>> On 04/03/2019 12:31, Jacques Le Roux wrote:
>>>> +1
>>>>
>>>> Jacques
>>>>
>>>> Le 04/03/2019 à 11:34, Jacopo Cappellato a écrit :
>>>>> I think that the simplest way to convey this message is to edit the README
>>>>> document with a link to OpenJDK rather than Oracle JDK.
>>>>>
>>>>> Jacopo
>>>>>
>>>>> On Mon, Mar 4, 2019 at 10:22 AM Jacques Le Roux <
>>>>> [hidden email]> wrote:
>>>>>
>>>>>> We should then make clear to our users that they will need to switch to
>>>>>> OpenJDK if they want free security support.
>>>>>>
>>>>>> I guess most are aware, but maybe not small companies or single users.
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>> Le 28/02/2019 à 18:48, Michael Brohl a écrit :
>>>>>>> +1 for Taher's suggestion.
>>>>>>>
>>>>>>> Thanks, Michael
>>>>>>>
>>>>>>> Am 28.02.19 um 12:32 schrieb Taher Alkhateeb:
>>>>>>>> Perhaps we can keep ofbiz 17.12 on java 8, and let 18.12 and trunk
>>>>>>>> switch to java 11 on openjdk. This might provide stability expected by
>>>>>>>> users as indicated by Michael.
>>>>>>>>
>>>>>>>> On Thu, Feb 28, 2019 at 2:27 PM Jacques Le Roux
>>>>>>>> <[hidden email]> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> During discussions in the "Oracle Java release model changes and
>>>>>> consequences for the project" thread, we created "Upgrade OFBiz to use Java
>>>>>> JDK
>>>>>>>>> Version 11" aka OFBIZ-10757.
>>>>>>>>>
>>>>>>>>> There we began to discuss not only if we should switch to Java 11 LTS
>>>>>> (Long Time Support), which is obviously the best current choice, but also
>>>>>> which
>>>>>>>>> Java JDK origin we should use OOTB.
>>>>>>>>>
>>>>>>>>> So we have few options and we should clarify what the community wants.
>>>>>>>>>
>>>>>>>>> Options are:
>>>>>>>>>
>>>>>>>>>     1. Do we agree to use https://adoptopenjdk.net/releases.html as
>>>>>> Java JDK origin OOTB?
>>>>>>>>>     2. Which branches should switch to Java1? Obviously the trunk and
>>>>>> R18 should. Should R17, which is not yet released, switch also?
>>>>>>>>> I hope we don't need a vote and will quickly find a consensus.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> Jacques
>>>>>>>>>

[Nicolas Malin-2]

On 13/04/2019 11:47, Jacques Le Roux wrote:
> I just tested, without surprise the trunk HEAD works with Java 11

I did the same with 18.12, works fine

Nicolas

[Jacques Le Roux]

If nobody disagree, I'll make the last move (ie ask for Java 11 in build.gradle) in 3 days

Jacques

Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
> On 13/04/2019 11:47, Jacques Le Roux wrote:
>> I just tested, without surprise the trunk HEAD works with Java 11
>
> I did the same with 18.12, works fine
>
> Nicolas
>
>

[Scott Gray-3]

That would probably halt any further contributions from me in the short to
medium term.

Can I ask why we need to require 11 when 8 is supported through to 2023?

Regards
Scott

On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <[hidden email]>
wrote:

> If nobody disagree, I'll make the last move (ie ask for Java 11 in
> build.gradle) in 3 days
>
> Jacques
>
> Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
> > On 13/04/2019 11:47, Jacques Le Roux wrote:
> >> I just tested, without surprise the trunk HEAD works with Java 11
> >
> > I did the same with 18.12, works fine
> >
> > Nicolas
> >
> >
>

[taher]

Well, I could be mistaken but it seems EOL for java 8 is coming soon (2019
commercial 2020 personal) [1]. This seems to be the case because the new
LTS is out which is java 11.

Also this new release model from oracle seems to be annoying which is
pushing developers to adopt the openjdk instead. So I guess the reason for
the upgrade is to strike two birds with one stone: upgrade java and switch
to openjdk.

With that being said, I don't have a firm opinion on upgrading and I just
wanted to highlight things, I leave it to other folks to decide.

[1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html

On Sun, Apr 14, 2019, 10:38 PM Scott Gray <[hidden email]>
wrote:

> That would probably halt any further contributions from me in the short to
> medium term.
>
> Can I ask why we need to require 11 when 8 is supported through to 2023?
>
> Regards
> Scott
>
> On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <[hidden email]>
> wrote:
>
> > If nobody disagree, I'll make the last move (ie ask for Java 11 in
> > build.gradle) in 3 days
> >
> > Jacques
> >
> > Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
> > > On 13/04/2019 11:47, Jacques Le Roux wrote:
> > >> I just tested, without surprise the trunk HEAD works with Java 11
> > >
> > > I did the same with 18.12, works fine
> > >
> > > Nicolas
> > >
> > >
> >
>

[jim.hinson]

FWIW, I think the move to Open JDK would be wise. Oracle doesn't have the best history of working with open source. I happened to be download the JDK this afternoon for something else, and received the notice below.

 

Jim

On 2019-04-14 17:09, Taher Alkhateeb wrote:

Well, I could be mistaken but it seems EOL for java 8 is coming soon (2019
commercial 2020 personal) [1]. This seems to be the case because the new
LTS is out which is java 11.

Also this new release model from oracle seems to be annoying which is
pushing developers to adopt the openjdk instead. So I guess the reason for
the upgrade is to strike two birds with one stone: upgrade java and switch
to openjdk.

With that being said, I don't have a firm opinion on upgrading and I just
wanted to highlight things, I leave it to other folks to decide.

[1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html

On Sun, Apr 14, 2019, 10:38 PM Scott Gray <[hidden email]>
wrote:

That would probably halt any further contributions from me in the short to
medium term.

Can I ask why we need to require 11 when 8 is supported through to 2023?

Regards
Scott

On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <[hidden email]>
wrote:

If nobody disagree, I'll make the last move (ie ask for Java 11 in
build.gradle) in 3 days

Jacques

Le 13/04/2019 à 12:34, Nicolas Malin a écrit :

On 13/04/2019 11:47, Jacques Le Roux wrote:

I just tested, without surprise the trunk HEAD works with Java 11

I did the same with 18.12, works fine

Nicolas

[Mathieu Lirzin]

Hello Scott,

Scott Gray <[hidden email]> writes:

> That would probably halt any further contributions from me in the short to
> medium term.
>
> Can I ask why we need to require 11 when 8 is supported through to 2023?

I was in a similar situation a few months ago because my GNU/linux
distro was not yet providing OpenJDK 11 out of the box, but this has
been fixed in the meantime.

Can you expand on what would precisely prevent you from contributing in
the short/medium term?  What would be your planning requirements in term
of upgrade to not block your contributions?

I think besides security support, upgrading to Java 11 has the benefit
of providing useful standard features available like:

    - Map and Set pseudo-literals
    - Modules
    - Standard HTTP client
    - Better type inference with the ‘val’ keyword.
    - More convenient higher-order methods (like ‘Predicate#not’)

Thanks.

--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

[Scott Gray-3]

My understanding was that openjdk would support java 8 until 2023.

In the past our strategy used to be that we should ensure the code base
would operate on newer java versions but keep our minimum required version
as low as possible.  That effectively allows users to run whatever version
they like.  So unless there are some compelling new features in java
9/10/11 that we think we must have, I'd prefer it if we kept our minimum
supported version as low as possible.

For myself, all client projects are still running java 8 (openjdk) so
before I could continue contributing to OFBiz I would have to figure out
how to run both versions on my machine with minimal disruption.  Since I
don't have a huge amount of spare time, I would probably just put it off
for quite a while and work on other things.

I'm not trying to veto the idea, if the community wants to proceed then it
should but I doubt I'm the only contributor we'd be putting another hurdle
in front of.

Regards
Scott

On Mon, 15 Apr 2019 at 09:09, Taher Alkhateeb <[hidden email]>
wrote:

> Well, I could be mistaken but it seems EOL for java 8 is coming soon (2019
> commercial 2020 personal) [1]. This seems to be the case because the new
> LTS is out which is java 11.
>
> Also this new release model from oracle seems to be annoying which is
> pushing developers to adopt the openjdk instead. So I guess the reason for
> the upgrade is to strike two birds with one stone: upgrade java and switch
> to openjdk.
>
> With that being said, I don't have a firm opinion on upgrading and I just
> wanted to highlight things, I leave it to other folks to decide.
>
> [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>
> On Sun, Apr 14, 2019, 10:38 PM Scott Gray <[hidden email]>
> wrote:
>
> > That would probably halt any further contributions from me in the short
> to
> > medium term.
> >
> > Can I ask why we need to require 11 when 8 is supported through to 2023?
> >
> > Regards
> > Scott
> >
> > On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <
> [hidden email]>
> > wrote:
> >
> > > If nobody disagree, I'll make the last move (ie ask for Java 11 in
> > > build.gradle) in 3 days
> > >
> > > Jacques
> > >
> > > Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
> > > > On 13/04/2019 11:47, Jacques Le Roux wrote:
> > > >> I just tested, without surprise the trunk HEAD works with Java 11
> > > >
> > > > I did the same with 18.12, works fine
> > > >
> > > > Nicolas
> > > >
> > > >
> > >
> >
>

[taher]

Hi Scott,

I'm not sure if this helps with running two versions simultaneously, but I
have multiple versions on my machine, and I setup the $JAVA_HOME to point
to /opt/jdk which in turn is a symlink to the JDK found in /opt/java/jdk8.
This way changing the jdk version is as fast as changing the symlink. I
even wrote a little script that looks up versions and I select the one most
appropriate.

Of course this is a side note, staying on Java 8 is fine by me given
getting more contributions from the community including yourself. I remain
on the fence.


On Mon, Apr 15, 2019, 1:08 AM Scott Gray <[hidden email]>
wrote:

> My understanding was that openjdk would support java 8 until 2023.
>
> In the past our strategy used to be that we should ensure the code base
> would operate on newer java versions but keep our minimum required version
> as low as possible.  That effectively allows users to run whatever version
> they like.  So unless there are some compelling new features in java
> 9/10/11 that we think we must have, I'd prefer it if we kept our minimum
> supported version as low as possible.
>
> For myself, all client projects are still running java 8 (openjdk) so
> before I could continue contributing to OFBiz I would have to figure out
> how to run both versions on my machine with minimal disruption.  Since I
> don't have a huge amount of spare time, I would probably just put it off
> for quite a while and work on other things.
>
> I'm not trying to veto the idea, if the community wants to proceed then it
> should but I doubt I'm the only contributor we'd be putting another hurdle
> in front of.
>
> Regards
> Scott
>
> On Mon, 15 Apr 2019 at 09:09, Taher Alkhateeb <[hidden email]>
> wrote:
>
> > Well, I could be mistaken but it seems EOL for java 8 is coming soon
> (2019
> > commercial 2020 personal) [1]. This seems to be the case because the new
> > LTS is out which is java 11.
> >
> > Also this new release model from oracle seems to be annoying which is
> > pushing developers to adopt the openjdk instead. So I guess the reason
> for
> > the upgrade is to strike two birds with one stone: upgrade java and
> switch
> > to openjdk.
> >
> > With that being said, I don't have a firm opinion on upgrading and I just
> > wanted to highlight things, I leave it to other folks to decide.
> >
> > [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
> >
> > On Sun, Apr 14, 2019, 10:38 PM Scott Gray <[hidden email]>
> > wrote:
> >
> > > That would probably halt any further contributions from me in the short
> > to
> > > medium term.
> > >
> > > Can I ask why we need to require 11 when 8 is supported through to
> 2023?
> > >
> > > Regards
> > > Scott
> > >
> > > On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <
> > [hidden email]>
> > > wrote:
> > >
> > > > If nobody disagree, I'll make the last move (ie ask for Java 11 in
> > > > build.gradle) in 3 days
> > > >
> > > > Jacques
> > > >
> > > > Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
> > > > > On 13/04/2019 11:47, Jacques Le Roux wrote:
> > > > >> I just tested, without surprise the trunk HEAD works with Java 11
> > > > >
> > > > > I did the same with 18.12, works fine
> > > > >
> > > > > Nicolas
> > > > >
> > > > >
> > > >
> > >
> >
>

[Jacques Le Roux]

Thanks Taher,

I believe it helps. Maybe you can share in tools?

I have something similar on Windows 7. A bit more convoluted because I copy the selected JDK on a RAM Disk (it's still faster than SSD
<https://dzone.com/articles/accelerating-build-using-ram-disk>) and switch between them with bat files.

My intent is to share the mechanism with the community. I know not much OFBiz dev work with Windows, but it seems more users are.

Jacques

Le 15/04/2019 à 09:34, Taher Alkhateeb a écrit :

> Hi Scott,
>
> I'm not sure if this helps with running two versions simultaneously, but I
> have multiple versions on my machine, and I setup the $JAVA_HOME to point
> to /opt/jdk which in turn is a symlink to the JDK found in /opt/java/jdk8.
> This way changing the jdk version is as fast as changing the symlink. I
> even wrote a little script that looks up versions and I select the one most
> appropriate.
>
> Of course this is a side note, staying on Java 8 is fine by me given
> getting more contributions from the community including yourself. I remain
> on the fence.
>
>
> On Mon, Apr 15, 2019, 1:08 AM Scott Gray <[hidden email]>
> wrote:
>
>> My understanding was that openjdk would support java 8 until 2023.
>>
>> In the past our strategy used to be that we should ensure the code base
>> would operate on newer java versions but keep our minimum required version
>> as low as possible.  That effectively allows users to run whatever version
>> they like.  So unless there are some compelling new features in java
>> 9/10/11 that we think we must have, I'd prefer it if we kept our minimum
>> supported version as low as possible.
>>
>> For myself, all client projects are still running java 8 (openjdk) so
>> before I could continue contributing to OFBiz I would have to figure out
>> how to run both versions on my machine with minimal disruption.  Since I
>> don't have a huge amount of spare time, I would probably just put it off
>> for quite a while and work on other things.
>>
>> I'm not trying to veto the idea, if the community wants to proceed then it
>> should but I doubt I'm the only contributor we'd be putting another hurdle
>> in front of.
>>
>> Regards
>> Scott
>>
>> On Mon, 15 Apr 2019 at 09:09, Taher Alkhateeb <[hidden email]>
>> wrote:
>>
>>> Well, I could be mistaken but it seems EOL for java 8 is coming soon
>> (2019
>>> commercial 2020 personal) [1]. This seems to be the case because the new
>>> LTS is out which is java 11.
>>>
>>> Also this new release model from oracle seems to be annoying which is
>>> pushing developers to adopt the openjdk instead. So I guess the reason
>> for
>>> the upgrade is to strike two birds with one stone: upgrade java and
>> switch
>>> to openjdk.
>>>
>>> With that being said, I don't have a firm opinion on upgrading and I just
>>> wanted to highlight things, I leave it to other folks to decide.
>>>
>>> [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>>>
>>> On Sun, Apr 14, 2019, 10:38 PM Scott Gray <[hidden email]>
>>> wrote:
>>>
>>>> That would probably halt any further contributions from me in the short
>>> to
>>>> medium term.
>>>>
>>>> Can I ask why we need to require 11 when 8 is supported through to
>> 2023?
>>>> Regards
>>>> Scott
>>>>
>>>> On Sun, 14 Apr 2019, 23:37 Jacques Le Roux, <
>>> [hidden email]>
>>>> wrote:
>>>>
>>>>> If nobody disagree, I'll make the last move (ie ask for Java 11 in
>>>>> build.gradle) in 3 days
>>>>>
>>>>> Jacques
>>>>>
>>>>> Le 13/04/2019 à 12:34, Nicolas Malin a écrit :
>>>>>> On 13/04/2019 11:47, Jacques Le Roux wrote:
>>>>>>> I just tested, without surprise the trunk HEAD works with Java 11
>>>>>> I did the same with 18.12, works fine
>>>>>>
>>>>>> Nicolas
>>>>>>
>>>>>>