Fixed
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
sh...@uber.com <sh...@uber.com> #3
Any update here? Seems like a rename mistake that can be fixed. Happy to contribute if the team doesn't have bandwidth
gh...@google.com <gh...@google.com> #4
Xav, should this be assigned to you / the Gradle team?
ne...@soundcloud.com <ne...@soundcloud.com> #6
This check fails the build when running the `generateDebugSources` task. This task is sometimes included in AS sync.
xa...@google.com <xa...@google.com> #7
This is fixed and will be in a 4.1 build coming out in couple of weeks
za...@gmail.com <za...@gmail.com> #8
Was sent here from
With kotlin 1.4.0 out now, local lint projects no longer work in AGP and fail the build. We still saw this behavior on 4.1 beta05 as well, and had to move our custom lints to a separate repo and just host their jar on an internal artifactory dependency
x-...@wealthfront.com <x-...@wealthfront.com> #9
Still seeing the same bug on AGP 4.1 and Kotlin 1.4.0 for our custom lint rules module.
hq...@gmail.com <hq...@gmail.com> #10
Please reopen this issue. The same bug is still in AGP 4.1.1 .
Edit: that might be related to Kotlin according to
Description
Now if i'm in my app module (or other Android library modules) I'd like to be able to mix-and-match these lint rules and apply them individually as needed.
dependencies {
lintChecks project(":lint-checks-rxjava")
lintChecks project(":lint-checks-android")
}
However, this causes an error
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':sample:prepareLintJar'.
> Found more than one jar in the 'lintChecks' configuration. Only one file is supported. If using a separate Gradle project, make sure compilation dependencies are using compileOnly
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
From talking to Jake, it seems like this is a bug from the configuration name change and this check should only apply to lintPublish