Closed csottile closed 2 years ago
The is no workaround. The specification says the 1.8.*
is not valid.
It therefore also does not specify how this value could be interpreted.
The only thing I can think of is changing the version string in the JNLP.
Hi We ecounterd the same problem described in issue #60 , but on a third party jnlp.
I understand my JNLP is out of standard, but I don't understand why it works on Oracle JWS.
How can we solve? Is there any workaround?
Logs:
I look forward to your kind feedback.
Best regards, Carmelo