Difference in Sage.jar between Windows and Linux builds
- Dominant language
- Java
- Stars
- 287
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
I have been working on rebuilding the Unraid Docker solution and was running into an issue with the Java8 docker as SageTV would run but a placeshifter would not connect. The issue was related to a change in Java between 8 and 9 and Byte(ByteBuffer).
The odd thing is I often test using Java 8 on windows and had no issues connection a placeshifter...both builds were the latest 9.2.6 releases.
So I copied the Sage.jar from the windows release into the linux docker and restarted SageTV and now I was able to connect the placeshifter to this Java 8 docker.
In my research I find that you can build a jar using JDK9 with the --release=8 option and it will resolve the Byte/ByteBuffer compatibility issue.
So are we using this --release option for the Windows jar build and not the Linux build or what is different in the 2 build processes that makes the Linux build fail on Java 8 but the Windows build works?
Thoughts?
Contributor guide
Assessment
This issue has not been assessed yet.