-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timber 4.7.1 appears to require JDK 1.8 #327
Comments
Hey, Can you check if adding this to your
The plain Timber implementation worked fine for me in a Kotlin-only project (with no explicit targetCompatibility set to 1.8), but it could be probably because Kotlin might include the needed stuff for JetBrains Annotations. Just wanted to check if this method works with your project. Thanks! |
@dgadelha Thanks for the suggestion but that didn't seem to help. I should note that I'm using an older version of gradle so technically I used:
but that should be equivalent. I also tried other variations on forcing a different version of the annotations, such as
Based on the output of |
@byencho Sad to hear it didn't help. Looks like we'd need to wait for an update from @JakeWharton then. Until a solution comes, I guess you can keep using the previous version of Timber. Thanks! |
confirmed here too :( |
I don't think I'm going to "fix" this. With AS / AGP 3.2 desugar has moved into D8 and should just work. With AS / AGP 3.1 you can enable it by setting |
OK, seems fair. Thanks for checking! I'll close this out. |
We have a project that is currently not compatible with JDK 1.8. When updating from version 4.7.0 to 4.7.1 we get the following error:
This appears to be related to the version bump for the Jetbrains annotations (28aa40a#diff-c197962302397baf3a4cc36463dce5eaL29). The docs for the annotations starting with version 16.0.1 mention they require JDK 1.8:
This is first mentioned at JetBrains/java-annotations@fda1bd2#diff-04c6e90faac2675aa89e2176d2eec7d8 .
Is JDK 1.8 meant to be an intentional dependency for Timber 4.7.1 and up?
The text was updated successfully, but these errors were encountered: