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.
This tries to address the problem I had in #4900
Essentially, our Gradle Plugin tests are currently running by fetching
detekt-cli
from Maven Central/Local. The problem is that once I bump the version andpublishToMavenLocal
during the release process, I'm effectivelly exposed to all the tests failures that got never reported onmain
as we're using a older version ofdetekt-cli
.With this PR, I'm bumping the version to use the "next", and forcing the
build
task to depend onpublishToMavenLocal
. This will make sure the Gradle Plugin tests on CI are effectively running on a locally crafted version of detekt-cli.I agree that this is not idea, as we should instead inject the class-path, but this is better than the status quo. Looking for opinions.
To reproduce this:
@ActiveByDefault
to theMissingPackageDeclaration
rule