Workaround for problems with java.classpath/classpath on java 9 #104
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 java 9 the java application and bootstrap classpath loaders are no longer subclasses of URLClassLoader. As a result the java.classpath/classpath function (used to scan for migrations in the classpath) returns an empty list.
This pull request works around the issue by using java.classpath/system-classpath (based on the java classpath property) to find directories / jars to scan.