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

runtime jdk requirement of java client (via mvnd.sh) should be aligned to JDK8 #669

Closed
gzm55 opened this issue Jul 31, 2022 · 3 comments
Closed

Comments

@gzm55
Copy link
Contributor

gzm55 commented Jul 31, 2022

Now java client (via mvnd.sh) requires JDK11, different with native mvnd and the embedded maven 3.8.5. This makes the user surprising in some production environments.

  • Native mvnd: requires JDK8
  • maven 3.8.5: requires JDK8
  • mvnd.sh: requires JDK11 ?
@ppalaga
Copy link
Contributor

ppalaga commented Aug 4, 2022

  • Native mvnd: requires JDK8

Well, strictly speaking, mvnd is a native executable not requiring any JRE to run. A VM (called Substrate) is embedded. The daemon started by that executable is fine with Java 8.

  • maven 3.8.5: requires JDK8
  • mvnd.sh: requires JDK11 ?

Yes, this is by design. The client requires some features not available in Java 8.

If you are on Mac M1 and you want to overcome this limitation, you may want to compile mvnd yourself following @orpiske 's script https://www.orpiske.net/2022/07/try-apache-maven-daemon/

We actually had a similar question before. Here is a dirty hack I recommended at that time: #547 (comment)

@ppalaga
Copy link
Contributor

ppalaga commented Aug 4, 2022

Maybe we should document the limitation in README.

@gnodet
Copy link
Contributor

gnodet commented Jan 24, 2023

I think this issue can now be closed with the merge of #717 and #722.

@gnodet gnodet closed this as completed Jan 24, 2023
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

No branches or pull requests

3 participants