-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Make build fail if using Android-incompatible JVM APIs/deps #49
Comments
Another related comment: |
Gradle setup is kinda described here: |
Creating an Android target might actually not be necessary nor desirable if we're not building an actual Android library (with manifest, potential R resources, etc.). Another option could be to use AnimalSniffer to check for old Android API usages EDIT: animal sniffer with Android signatures might be only useful for detecting usages of Android-specific APIs, but might not detect the use of unsupported Java features. To be double checked. Not that Java 9+ APIs would be detected via toolchains anyway. |
Based on this slack conversation, there should be a way to define an Android target (making use of the Android toolchain) in the build, so that using incompatible JVM dependencies or APIs fails the build.
An attempt lives here: 5f27a77
But it requires actually installing the android toolchain locally and in the CI, and may not be worth it for now until people upvote this issue.
The text was updated successfully, but these errors were encountered: