Fix kastree on Java 11. #41
Open
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
Author
|
We use kastree for https://github.com/dropbox/hypershard-android. I'd love to move to https://github.com/kotlinx/ast, but it runs on a newer kotlin runtime than we're using (we're still on 1.4), and it looks like there's only jitpack nightlies. Would love any advice you have here, but it'd be awesome if you pushed this fix up to Maven Central. Thanks! |
Owner
|
@yanks - I am no longer really maintaining this. I would happily link to a fork though, but otherwise I'm afraid I can't even commit to a merge and push the maven central. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When running kastree on Java 11, an error occurs; it looks something like this:
Exception in thread "main" java.lang.IllegalStateException: LOGGING: Loading modules: [<snip>] (no MessageCollector configured)This fixes this issue by adding a blackhole collector.