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

Simplify appending to env var JAVACMD_OPTIONS #96

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

aureliojargas
Copy link

In default Bash, it is not an error to refer to an undeclared (or empty) variable. In that case, it will just expand to an empty string.

So there's no need to do the prior check, you can just append the new value right away.

Also, in Bash you can safely set and export on the same command.

In default Bash, it is not an error to refer to an undeclared (or empty)
variable. In that case, it will just expand to an empty string.

So there's no need to do the prior check, you can just append the new value
right away.

Also, in Bash you can safely set and export on the same command.
@jongiddy
Copy link
Contributor

Thanks. I love the conciseness of this! PR #90 adds -o nounset to this file, so when that is merged, this won't work as is. But it could still be a one-liner.

@aureliojargas
Copy link
Author

aureliojargas commented Mar 22, 2018

@jongiddy thanks for the heads-up!

In that case, the ${foo:-} parameter expansion should do the trick to avoid raising error when unset.

Since it will also work even when -o nounset is not active, I'll update this PR with the fix.

PR bmwcarit#90 will add "-o unset" to this file, so we need this variable expansion to
guard when the $JAVACMD_OPTIONS is unset.
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