lint
Latest Update | Stable Release | Release Candidate | Beta Release | Alpha Release |
---|---|---|---|---|
September 4, 2024 | - | - | - | 1.0.0-alpha02 |
Declaring dependencies
To add a dependency on Lint, you must add the Google Maven repository to your project. Read Google's Maven repository for more information.
Add the dependencies for the artifacts you need in the build.gradle
file for
your app or module:
Groovy
plugins { id("com.android.lint") } dependencies { lintChecks "androidx.lint:lint-gradle:1.0.0-alpha02" }
Kotlin
plugins { id("com.android.lint") } dependencies { lintChecks("androidx.lint:lint-gradle:1.0.0-alpha02") }
For more information about dependencies, see Add build dependencies.
Feedback
Your feedback helps make Jetpack better. Let us know if you discover new issues or have ideas for improving this library. Please take a look at the existing issues in this library before you create a new one. You can add your vote to an existing issue by clicking the star button.
See the Issue Tracker documentation for more information.
There are no release notes for this artifact.
Version 1.0
Version 1.0.0-alpha02
September 4, 2024
androidx.lint:lint-gradle:1.0.0-alpha02
is released. Version 1.0.0-alpha02 contains these commits.
New Features
- Added a check for discouraged
GradleRunner.withPluginClasspath
API. - Added checks for APIs that are problematic for lazy configuration by flagging calls to
TaskContainer.withType
without callingconfigureEach
.- Added checks for APIs that are problematic for Gradle Project Isotation by flagging calls to
Project.getRootProject
,Project.findProject
,Project.getParent
,Project.findProperty
,Project.getProperties
,Project.hasProperty
,Project.property
.
- Added checks for APIs that are problematic for Gradle Project Isotation by flagging calls to
Version 1.0.0-alpha01
February 21, 2024
androidx.lint:lint-gradle:1.0.0-alpha01
is released. Version 1.0.0-alpha01 contains these commits.
New Features
- An initial set of lint checks for Gradle Plugin authors to help them catch mistakes in their code. They are expected to be used on Gradle projects that apply
java-gradle-plugin
. It will catch uses of internal Gradle and Android Gradle Plugin APIs and eager task configuration.