Fix creation of URLClassLoader #1331
Merged
Conversation
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
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.
With the current URLClassLoader initialisation, it has the system class loader as a parent. Due to the implementation of the Java class loaders, when loadClass() is invoked, it calls the parent loadClass() method first. So, in our case, when loading up a class coming from a jar file, it is resolved first by the system class loader and if it can't resolve it - uses the URLClassLoader. This is not a problem in most cases, however when parsing classes coming from a jar file which can also be found in the SBG dependencies, class versioning problems may occur.