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

DTC_JAVA_HOME should supersede JAVA_HOME #1270

Open
ascheman opened this issue Oct 29, 2023 · 0 comments
Open

DTC_JAVA_HOME should supersede JAVA_HOME #1270

ascheman opened this issue Oct 29, 2023 · 0 comments

Comments

@ascheman
Copy link
Contributor

Describe the bug

If JAVA_HOME is set (e.g., by sdkman), and DTC_JAVA_HOME is explicitely set or computed by DTC, the latter should be used.

To Reproduce
Steps to reproduce the behavior:

  1. Install local (DTC) Java: dtcw install java -> results in ~/.doctoolchain/jdk
  2. Set JAVA_HOME to a different directory (or simply use SDKMAN
  3. Run ./dtcw local generateSite -> Will use the Java from ${JAVA_HOME} instead of the one installed by step one.
  4. On many systems/architectures this might work perfectly without problems. On Apple Silicon this might result in a Gradle error Can't load library: ... (since JBake still uses an x86_64 native library).
ascheman added a commit that referenced this issue Oct 29, 2023
during doctoolchain script execution.
ascheman added a commit that referenced this issue Oct 29, 2023
and override JAVA_HOME setting.
ascheman added a commit that referenced this issue Oct 29, 2023
during doctoolchain script execution.
ascheman added a commit that referenced this issue Oct 29, 2023
and override JAVA_HOME setting.
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

1 participant