Set minimum java to 171

[tobiasdiez]

Fixes #4093. Since Java does not automatically update to 171, users have to manually install the 172 update. This is very convenient.

I actually propose to cherry-pick this PR to 4.x and immediately release 4.3.1.

---

• Change in CHANGELOG.md described
• Tests created for changes
• Manually tested changed features in running JabRef
• Screenshots added in PR description (for bigger UI changes)
• Ensured that the git commit message is a good one
• Check documentation status (Issue created for outdated help page at help.jabref.org?)

[stefan-kolb]

Let me check if the fix is already included in _171

[stefan-kolb]

https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8195830

Unfortunately this is only fixed in 8u172 b01.
Can't see v171 there tho.

Results:

8u151: OK
8u152: OK
8u161: FAIL
8u162: FAIL
8u172 b03: OK
9.0.4: OK
10 ea b39: OK

Unfortunately, I cannot find any information about v171.
We porbably need to install and check it manually.

[koppor]

For provenance: This downgrades the minimum Java version introduced at #4058.

[Siedlerchr]

Have you looked at the oracle changelog page for 171? Where you download the jdk there is a changelog linked. It could be that 171 only includes security fixes

[koppor]

For a quick try out: choco install jre8. This installs Java 8 171. See https://chocolatey.org/packages/jre8.

Deep link to the Changelog:

• 171: http://www.oracle.com/technetwork/java/javase/8u171-relnotes-4308888.html
• 172: http://www.oracle.com/technetwork/java/javase/8u172-relnotes-4308893.html

The Changelog of 172 shows:

The changes made under JDK-8033530 introduced an inconsistency between the implementation for and the documentation of the following methods:

However, JDK-8033530 is not listed in the Changelog for 171. I would assume nevertheless that this issue is fixed in 171. See #4058 (comment).

[stefan-kolb]

Ok, I have also tried to reproduce the bug with v171 and the code from https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8195830. Cannot see any spikes right now. We cannot be 100% sure as it is not in the changelog, but maybe it is worth risking it until v172 is rolled out everywhere. i guess we should still force v172 later on.

[koppor]

Backported to v4.x at 3f73e9e.