[MAGNOLIA-5959] Fix faulty JDK check for JDKs that actually work Created: 23/Oct/14 Updated: 03/Nov/14 Resolved: 03/Nov/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Daniel Lipp |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac OS X 10.9.5 with JDK 1.7.0_72 |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I attempted to run a Magnolia 5.3.1-based snapshot (providing autosuggest, available here) and got the attached error message. The message says that I have to update my JDK (or set 'magnolia.allow.problematic.environment=true'), but the mentioned wiki page claims that the problem has been fixed with my JDK version. That JDK check seems to be faulty and should be fixed. |
| Comments |
| Comment by Daniel Lipp [ 03/Nov/14 ] |
|
There's nothing wrong with the check - it's just that the adaption was done with |