-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with multiproject without build.gradle
in root.
#137
Comments
Such as muli project builds Issue: gradle#137 Signed-off-by: Andrés Alcarraz <[email protected]>
build.gradle
in root.build.gradle
in root.
Hi! We're facing the same issue and would like to see this fixed. Do you need any help with your pull request? |
Ok, actually, what I found out is that the culprit is this command
|
Hi, this was working wonderfully for me until now, thank you for the great work.
I started a multi project build according to Structuring and Building a Software Component with Gradle
and it doesn't have a
build.gradle
in the project root. Thegradle init
command doesn't generate abuild.gradle
in the project root, either.In that case, the
gradle-completion
doesn't find the build file and defaults to assuming it is not an initializedgradle
project, giving only the common options.Maybe it can be assumed that if the settings file is found, the project is initialized, even if the build file is not found? I'm willing to add a PR, or a patch, if I manage to solve this and it works.
I found a workaround for this creating an empty
build.gradle
, but before that, well I'll tell the story because it may be worthy to add a warning or something in theREADME.md
about that.There is also the possibility that the script works, and somehow I did something to break it, in that case, please excuse me and let me know.
To reproduce, try this:
And then try to autocomplete gradle there. It will only show the default tasks.
The text was updated successfully, but these errors were encountered: