{{ message }}
Allow upgrade tool to use a local directory of h2 release jars instead requiring network connectivity to mavencentral#4229
Open
funkyjive wants to merge 1 commit into
Open
Conversation
…, allow the user to specify a directory in system property 'h2LocalJars' that can be used with the upgrade tool. Jars should be in their original released names h2-major#.minor#.build#.jar
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In some security environments, network access to maven central has been removed. This PR adds an optional system property named "h2LocalJars" which, if set, causes the Upgrade tool to search that directory for the jar. An application can keep all past jars that it used available and then the tool could be used to upgrade them without requiring any download access.
Here is the idea, change anything you wish.