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

Don't search for java command in legacy locations #121

Open
mizdebsk opened this issue Oct 4, 2024 · 3 comments
Open

Don't search for java command in legacy locations #121

mizdebsk opened this issue Oct 4, 2024 · 3 comments

Comments

@mizdebsk
Copy link
Member

mizdebsk commented Oct 4, 2024

Currently the java command is searched in the following locations under JAVA_HOME:

  • jre/sh/java - old IBM Java, at least on AIX
  • jre/bin/java no longer relevant since Jigsaw (Java >= 9)
  • bin/java - still used

bin/java is the only one currently used. Therefore Javapackages should look for java command only under ${JAVA_HOME}/bin/java and ignore the other two locations.

@fridrich
Copy link
Contributor

fridrich commented Oct 4, 2024

This will not work for me here if there is only java-1_8_0-openjdk package installed. I have some users that insist using that on some systems :)

@fridrich
Copy link
Contributor

fridrich commented Oct 4, 2024

OK, if there is no other java-N-openjdk installed, it would work through the /usr/bin/java alternative. But in other situations, it would mean that they have to change their scripts to set it to the jre subdir.

@mizdebsk
Copy link
Member Author

mizdebsk commented Oct 4, 2024

Right, this is scoped for next major release (7.0.0) when we can assume that Java 8 is no longer relevant. On older systems javapackages 6.x can still be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants