Env. windows7/64 (2 PCs) & Version: 18.104.22.168 (x64)
Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
CPU threads: 2; OS: Windows 6.1; UI render: default;
Locale: fr-FR (fr_FR); Calc: group threaded
AdoptOpenJDK is not recognized as JRE => warning message:
*The folder you selected does not contain a Java runtime environment. Please select a different folder.*
Tried with OpenJDK8U-jre_x64_windows_hotspot_8u212b03.msi and also by downloading OpenJDK8U-jre_x64_windows_hotspot_8u212b03.zip and unzipping it in the Java folder.
Steps to Reproduce:
1. Install the jre (either by the installation program or by unzipping)
3. Tick Use a Java runtime environment (JRE).
AdoptOpenJDK does not appear in the list.
Click the Add button to add a JRE, navigate & select the jre folder.
Error message: The folder you selected does not contain a Java runtime environment. Please select a different folder
User Profile Reset: Yes
OpenGL enabled: Yes
Download site: https://adoptopenjdk.net/releases.html#x64_win
Also reproduced: https://ask.libreoffice.org/en/question/183834/how-can-i-use-adoptopenjdk-as-the-jre/?comment=191852#post-id-191852
Confirmed on Windows 10 Home en-US 64-bit (1809) with
Version: 22.214.171.124 (x64)
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
However, the AdoptOpenJDK is recognized with current master/6.3.0 for both x86 and x64 installs of AdoptOpenJDK 11 LTS
While not technically a dupe, believe this is also fixed against 6.1.6, 6.2.4 and master/6.3.0 by work on See Also bug 124503
(In reply to pierre-yves samyn from comment #0)
> Env. windows7/64 (2 PCs) & Version: 126.96.36.199 (x64)
> Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
> CPU threads: 2; OS: Windows 6.1; UI render: default;
> Locale: fr-FR (fr_FR); Calc: group threaded
> AdoptOpenJDK is not recognized as JRE => warning message:
That would mean that <https://gerrit.libreoffice.org/plugins/gitiles/core/+/d801075217375a79ca037df96b3adff5eee5ebd2%5E%21> "Support AdoptOpenJDK", included in libreoffice-6-1-5 (prior to tag libreoffice-188.8.131.52), does not work as intended.
(Which would be somewhat irrelevant as the fix for bug 124503 should indeed get this fixed, through a different internal approach, for LO 6.1.6, but would still be worrisome.)
add to CC
Created attachment 151407 [details]
Screenshot of AdoptOpenJDK displaying as a JRE in LibreOffice 184.108.40.206
This bug is no longer reproducible in
Version: 220.127.116.11 (x64)
Build ID: 170a9c04e0ad25cd937fc7a913bb06bf8c75c11d
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
Locale: en-GB (en_GB); UI-Language: en-GB
It appears to have been fixed in:
In bug 124503, through commit https://gerrit.libreoffice.org/plugins/gitiles/core/+/3d27b2fa9c5a03f78e5145377402f8a88e3da1be%5E%21
Technically, the solution used in that bug is *slightly* different, in that, rather than adding AdoptOpenJDK to the hardcoded supported list as requested in this bug, LibreOffice now assumes that every JVM not in the hardcoded list that reports that it is compatible with Java 6 at a minimum are usable as a JVM. As a result, this bug is no longer reproducible in all supported and development branches.
Changing status to RESOLVED WORKSFORME.
I confirm RESOLVED WORKSFORME on windows 7/64 with
Version: 18.104.22.168.alpha1+ (x64)
Build ID: f5b9590fc06811a9dff550c6998d1d1088507e23
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-05-23_22:33:02
Locale: fr-FR (fr_FR); UI-Language: en-US
Confirm problem. OS and LO versions:
OpenSUSE Tumbleweed x86_64 current as of right now.
(In reply to Kenneth from comment #7)
> Confirm problem. OS and LO versions:
> OpenSUSE Tumbleweed x86_64 current as of right now.
...which would be a further data point, in line with comment 2, suggesting that <https://gerrit.libreoffice.org/plugins/gitiles/core/+/273330a55d7cf457da6d7ba9829527a961c40bc0%5E%21> "Support AdoptOpenJDK", which should have fixed this on libreoffice-6-2 towards LO 6.2.1, does not work as intended. (Which, again, "would be somewhat irrelevant as the fix for bug 124503 should indeed get this fixed, through a different internal approach," for LO 6.2.4.)
Or, Kenneth, I completely miss what you wanted to express with comment 7.