Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require Java 8+ instead of Java 11+ at runtime #56

Closed
ppalaga opened this issue Aug 14, 2020 · 0 comments · Fixed by #57
Closed

Require Java 8+ instead of Java 11+ at runtime #56

ppalaga opened this issue Aug 14, 2020 · 0 comments · Fixed by #57
Milestone

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Aug 14, 2020

We require Java 11 at runtime since #55 where we started using ProcessHandle.current().info().command(). Because it is just the client code, we could do some module splitting and require Java 11 only for the compilation of that code. The resulting native executable is java-version agnostic and the rest of the jars could then be runnable on Java 8.

@ppalaga ppalaga changed the title Java 8 should suffice at runtime Require Java 8+ instead of Java 11+ at runtime Aug 14, 2020
ppalaga added a commit to ppalaga/mvnd that referenced this issue Aug 14, 2020
ppalaga added a commit that referenced this issue Aug 14, 2020
Fix #56 Require Java 8+ instead of Java 11+ at runtime
@ppalaga ppalaga added this to the 0.0.3 milestone Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant