-
Notifications
You must be signed in to change notification settings - Fork 700
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
Normalize extendedJavaHome environment variable #78
Conversation
The extendedJavaHome environment variable contains `.` symbols in the version. This causes the environment variable to be ignored by the action runner. It's best to replace those and other non standard symbols with and underscore. For reference: > Environment variable names used by the utilities in the Shell and Utilities volume of IEEE Std 1003.1-2001 consist solely of uppercase letters, digits, and the '_' (underscore) from the characters defined in Portable Character Set .
// uppercase letters, digits, and the underscore. Therefore we convert | ||
// the extendedJavaHome variable to upper case and replace '.' symbols and | ||
// any other non-alphanumeric characters with an underscore. | ||
extendedJavaHome = extendedJavaHome.toUpperCase().replace(/[^0-9A-Z_]/g, '_'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a breaking change. Should the old variable be set also, so existing customers dont get broken?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. It could break certain users if they're actually able to use the current variable.
When we eventually release a v2 version of setup-java, then we can remove the old one (we don't promise compat between the new versions).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, I just pushed a new commit that keeps the old variable.
The extendedJavaHome environment variable contains
.
symbols in the version.This causes the environment variable to be ignored by the action runner.This makes the variable inaccessible withbash
's${VAR}
syntax . It's best to replace those and other non standard symbols with and underscore.For reference:
See also: https://unix.stackexchange.com/questions/93532/exporting-a-variable-with-dot-in-it