#8 support alternate env var ${TOOL}_DEFAULT_HOME if ${TOOL}_HOME cant be used #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # grails
…es if more than one tool version is used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#8 In case you use many different Grails versions for different projects, you might not be able to use a fixed GRAILS_HOME env var, as this can lead to clashes (e.g. if your use Grails 2 and Grails 3 projects). Therefore I added another env var named ${TOOL}_DEFAULT_HOME to define e.g. the default Grails version to use without clashing with other Grails versions used.
e.g. if you set GRAILS_DEFAULT_HOME="/x/y/z/grails-2.4.4", this version is used if no version can be obtained.