Skip to content
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

Drop unneded kotlin dep #28375

Merged
merged 4 commits into from
Aug 31, 2021
Merged

Drop unneded kotlin dep #28375

merged 4 commits into from
Aug 31, 2021

Conversation

dnfield
Copy link
Contributor

@dnfield dnfield commented Aug 30, 2021

This was added to avoid warnings given about the wrong kotlin runtime version - upstream dependencies have again changed and it's no longer needed.

I think ideally we'd be passing the right -language-version argument, but I really don't know how to do that properly for gradle. Maybe @blasten knows.

@jason-simmons
Copy link
Member

Actually it looks like the "Runtime JAR files in the classpath have the version 1.4" warnings are still happening in the presubmit LUCI builders:

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8837435015190428721/+/u/build_android_debug/stdout

@dnfield
Copy link
Contributor Author

dnfield commented Aug 30, 2021

@blasten do you know any Gradle voodoo for this?

@blasten
Copy link

blasten commented Aug 31, 2021

@dnfield
Copy link
Contributor Author

dnfield commented Aug 31, 2021

@blasten yes, but those seem to be JVM parameters rather than parameters to pass to the Kotlin compiler.

@blasten
Copy link

blasten commented Aug 31, 2021

@dnfield what about this ?:

compileKotlin {
    kotlinOptions {
        languageVersion = '<version>' 
    }
}

@dnfield
Copy link
Contributor Author

dnfield commented Aug 31, 2021

@dnfield
Copy link
Contributor Author

dnfield commented Aug 31, 2021

Unfortunately this means we have to use the kotlin plugin which means we have to take more dependencies, but this is now passing locally with no warnings.

@blasten - do we get much value from using leakcanary?

@blasten
Copy link

blasten commented Aug 31, 2021

Ideally, we keep leakcanary. We don't use it a lot, but it's worth doing more memory-leak tests in the future.

@dnfield dnfield added the waiting for tree to go green This PR is approved and tested, but waiting for the tree to be green to land. label Aug 31, 2021
Copy link

@blasten blasten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes waiting for tree to go green This PR is approved and tested, but waiting for the tree to be green to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants