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

Confusing message about JAVA_HOME #1305

Closed
mhsmith opened this issue Jun 8, 2023 · 0 comments · Fixed by #1306
Closed

Confusing message about JAVA_HOME #1305

mhsmith opened this issue Jun 8, 2023 · 0 comments · Fixed by #1306
Labels
bug A crash or error in behavior. macOS The issue relates to Apple macOS support.

Comments

@mhsmith
Copy link
Member

mhsmith commented Jun 8, 2023

Describe the bug

I got this message on macOS:

*************************************************************************
** WARNING: JAVA_HOME does not point to a Java 17 JDK                  **
*************************************************************************

    Android requires a Java 17 JDK, but the location pointed to by the
    JAVA_HOME environment variable:

    /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home

    isn't a Java 17 JDK (it appears to be Java 1.8.0_352).

    Briefcase will use its own JDK instance.

This didn't make any sense, because I didn't have any JAVA_HOME environment variable. It turns out it was actually getting the path by running /usr/libexec/java_home.

Steps to reproduce

  • Install a Java version other than 17, and make sure its location is returned by /usr/libexec/java_home
  • Remove or rename Briefcase's existing Java 17 installation, if any
  • Unset JAVA_HOME
  • Run briefcase build android

Expected behavior

The message should correctly indicate where the path came from.

Screenshots

No response

Environment

  • Operating System: macOS
  • Python version: 3.8
  • Software versions:

Logs

No response

Additional context

No response

@mhsmith mhsmith added bug A crash or error in behavior. macOS The issue relates to Apple macOS support. labels Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A crash or error in behavior. macOS The issue relates to Apple macOS support.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant