Use the version catalog as the source of truth for plugin IDs #648
+85
−76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….gradle.lint` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.spotless` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.detekt` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.dependency-graph-generator` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.common.ui` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.common.library.android` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
….gradle.base` Aligned with issue serbelga#646, replaced the direct plugin ID declaration with the version catalog alias `libs.plugins.dev.sergiobelda.gradle.lint`. This ensures the plugin IDs in the build logic match the version catalog as the single source of truth, reducing duplication and improving maintainability.
|
I checked this gradle task and It's Ok. What should I do? |
|
I think build is failing because is trying to use a GitHub secret on a forked repository |
|
I will run locally these tasks and update the trigger to not use this secret on pull request that comes from a fork |
You are right, I have seen this type of error on another project |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The IDs stated in the build-logic build script must exactly match the plugin IDs in the version catalog file. This solution reduces the inherent duplication.
To avoid any IDE errors about missing plugin accessors when adding new plugins to the build-logic script, adding the new ID in the version catalog first is recommended, then invoking Gradle (sync) to generate the accessor classes.