question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

installKotlinterPrePushHook not working using 2.4.0

See original GitHub issue
➜  escape_pod git:(update_ktlint) ./gradlew installKotlinterPrePushHook

FAILURE: Build failed with an exception.

* What went wrong:
Task 'installKotlinterPrePushHook' not found in root project 'escape_pod'.

* Try:
Run gradlew tasks to get a list of available tasks. 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.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 4s

Let me know if you need more information

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:15 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
shabtaisharoncommented, Jun 19, 2020

yep, i can see it now

Build Setup tasks
-----------------
init - Initializes a new Gradle build.
installKotlinterPrePushHook - Installs Kotlinter Git pre-push hook
wrapper - Generates Gradle wrapper files.
1reaction
jeremymailencommented, Jun 18, 2020

Actually, I have a thought: is apply plugin: "org.jmailen.kotlinter" and apply plugin: 'kotlin' present for the root project as well? That would cause the hook task to be missing. Quite understandable since the root project probably doesn’t have kotlin source code, although it would be harmless to include it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Gradle problem :Could not resolve all files for configuration ...
Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files ...
Read more >
Build failed on Apple M1 with JDK8-arm64 [174695268]
If the mentioned workarounds are not working, I recommend using this workaround instead, adding it to the root build.gradle. This will force using...
Read more >
Gradle 6.7 Release Notes
This release comes with usability and performance improvements for the configuration cache. Early adopters of configuration cache can use the command line ...
Read more >
Using kapt | Kotlin
If you run into any problems with caching for annotation processors, disable caching for them: # specify annotation processors' full names ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found