You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Detekt 1.0.0-RC15, used in the index management build process for detecting code smells, fails to run due to not being able to resolve the detekt dependency jcommander 1.74. This dependency, jcommander 1.74, does not exist on maven central, and can only be resolved through jcenter. As jcenter is sunset, this dependency may never be resolved, so detekt must be upgraded to a version which doesn't include this dependency, or disabled. In later versions of detekt, the jcommander dependency was moved to version 1.72, so upgrading detekt should resolve this issue.
As upgrading detekt adds new code style checks, additional work will be needed to fix the newly found code smells to enable the detekt check to pass.
To Reproduce
Steps to reproduce the behavior:
./gradlew build or ./gradlew detekt fail due to a missing detekt dependency
> Task :detekt FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':detekt'.
> Could not resolve all files for configuration ':detekt'.
> Could not find com.beust:jcommander:1.74.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/com/beust/jcommander/1.74/jcommander-1.74.pom
- file:/home/runner/.m2/repository/com/beust/jcommander/1.74/jcommander-1.74.pom
- https://aws.oss.sonatype.org/content/repositories/snapshots/com/beust/jcommander/1.74/jcommander-1.74.pom
Required by:
project : > io.gitlab.arturbosch.detekt:detekt-cli:1.0.0-RC15
Remediation
To fix this issue:
Upgrade detekt to a version which uses jcommander 1.72
Backport the upgraded detekt version to the 1.2 branch, raise the allowed weighted issues count to enable building OR disable detekt entirely on the 1.2 branch Disables detekt due to missing dependencies #250
Additional context
As jcommander 1.74 is not on maven central, the jcenter workaround described here opensearch-project/opensearch-build#1456 does not help resolve the dependency.
The text was updated successfully, but these errors were encountered:
Describe the bug
Detekt 1.0.0-RC15, used in the index management build process for detecting code smells, fails to run due to not being able to resolve the detekt dependency jcommander 1.74. This dependency, jcommander 1.74, does not exist on maven central, and can only be resolved through jcenter. As jcenter is sunset, this dependency may never be resolved, so detekt must be upgraded to a version which doesn't include this dependency, or disabled. In later versions of detekt, the jcommander dependency was moved to version 1.72, so upgrading detekt should resolve this issue.
As upgrading detekt adds new code style checks, additional work will be needed to fix the newly found code smells to enable the detekt check to pass.
To Reproduce
Steps to reproduce the behavior:
./gradlew build or ./gradlew detekt fail due to a missing detekt dependency
Remediation
To fix this issue:
Additional context
As jcommander 1.74 is not on maven central, the jcenter workaround described here opensearch-project/opensearch-build#1456 does not help resolve the dependency.
The text was updated successfully, but these errors were encountered: