Improve usage of class loaders #167
Merged
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.
Class loaders are not discarded after use, but kept cached, so that subsequent use of the same class loader can reuse already loaded (and possibly JIT-compiled) classes.
Tool class loaders are separated from combined tool-project class loaders, so that tool class loaders can be reused when the same tool is ran on different projects.
Combined tool-project class loader is not even created unless particular tool is annotated with
@ProjectClassScope, which means that the tool needs a class loader that includes project classes.