Add build tool fallbacks for tasks#213
Merged
tartarughina merged 1 commit intozed-extensions:mainfrom Mar 14, 2026
Merged
Conversation
|
We require contributors to sign our Contributor License Agreement, and we don't have @mweirauch on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'. |
Contributor
Author
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
This also changes gradle project detection to check for `build.gradle` and `build.gradle.kts` instead of `gradlew` in the first place.
mweirauch
force-pushed
the
add-build-tool-fallbacks
branch
from
1f37273 to
84bd7a9
Compare
Collaborator
|
Thanks for these improvements and the addition of Gradle Kotlin |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 adds
mvnandgradlefallbacks for projects where no Maven Wrapper or Gradle Wrapper is present.This was tested with 5 simple test projects. (mvn, mvnw, gradle, gradle-kts, gradlew each with a main class, a test class and inner tests)
I took the liberty to adjust the message when no build tooling is found from "No build system found" to "No build tool found" as these are rather tools than complete "build systems".
EDIT: Updated to support Kotlin DSL (build.gradle.kts) based projects.