Fixed
Status Update
Comments
gh...@google.com <gh...@google.com> #2
Note: it looks like that hardcoded path may have changed recently to
build/intermediates/lint_jar/global/prepareLintJar/
which is breaking IDE support for custom checks.
build/intermediates/lint_jar/global/prepareLintJar/
which is breaking IDE support for custom checks.
xa...@google.com <xa...@google.com>
gh...@google.com <gh...@google.com> #3
Notes: this bug is the root cause of the recent https://b.corp.google.com/issues/123377555 , which is due to the recently added lintPublish configuration (https://b.corp.google.com/issues/65248347 ).
Once this bug is fixed we can fix the two workarounds in LintClient.kt (search for this bug number to find them.) I'd be happy to do that part if desired.
Once this bug is fixed we can fix the two workarounds in LintClient.kt (search for this bug number to find them.) I'd be happy to do that part if desired.
lk...@google.com <lk...@google.com> #4
Ping to Ed, CC udam. Any update on progress here?
ek...@google.com <ek...@google.com> #5
Ah, sorry. I have a pending CL. I'll try get some clarification on the comments in it.
gh...@google.com <gh...@google.com> #6
Just a heads up, this broke custom Lint checks again (see b/146403481 ).
(We had a regression test, but it does not check for backwards compatibility with previous Gradle versions, which is what broke in this case).
(We had a regression test, but it does not check for backwards compatibility with previous Gradle versions, which is what broke in this case).
Description
lintChecks project(':our-lint-checks')
This should be exposed in the builder-model such that lint can find them (right now it's hardcoded a search in build/intermediates/lint/ ).
It will also let the IDE look through the model and determine whether there are any custom checks that need to be compiled before Analyze > Inspect Code is run (and potentially to have a lint check that looks to see if the lint source code is newer than the jar to warn about it.)