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 <scott.g...@hotwaxsystems.com>
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 <slidingfilame...@gmail.com>
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 <scott.g...@hotwaxsystems.com>
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, <
jacques.le.r...@les7arts.com>
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
