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

Let JRE be selected via shell variable on debian #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

callegar
Copy link
Owner

An issue with openjdk 10 prevents jitsi from running on debian derivatives (including ubuntu bionic) where the system is configured
to run the java binary from openjdk 10 (see bug jitsi#530). Unfortunately, this is the default for ubuntu bionic.

Let the user decide which jre to use with jitsi via shell variable JITSI_JRE_HOME, so that it is possible to install Java 8 on ubuntu and use it with jitsi, without having to make the whole system default to Java 8 or without forcing the user to edit the jitsi script.

For instance, with this patch, one can say:

JITSI_JRE_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64/jre jitsi

An issue with openjdk 10 prevents jitsi from running on debian derivatives (including ubuntu bionic) where the system is configured
to run the java binary from openjdk 10 (see bug jitsi#530).  Unfortunately, this is the default for ubuntu bionic.

Let the user decide which jre to use with jitsi via shell variable JITSI_JRE_HOME, so that it is possible to install Java 8 on ubuntu and use it with jitsi, without having to make the whole system default to Java 8 or without forcing the user to edit the jitsi script.

For instance, with this patch, one can say:

JITSI_JRE_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64/jre jitsi
@traud
Copy link

traud commented Jan 23, 2020

  1. Just out of curiosity, why did you choose JITSI_JRE_HOME and not JAVA_HOME?
  2. Did you sign the Contributor License Agreement (CLA)?
    In that case, please, add a comment to your Pull Request.

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 this pull request may close these issues.

2 participants