Bootstrap Gradle(w)

[xenoterracide]

So in situation where I don't have gradle installed, I'm starting a new module/repo so no gradlew. And lets say for the sake of argument I don't have an IDE because I'm a CLI junky. The only real way to start that I can find is to install gradle.

However I think there could be a better way (note: I'm ok with doing this in a way that requires recent versions of java (8 or even 11). a way to fetch a bootstrapper curl https://gradle.com/bootstrap.sh | sh which might then fetch an archive of gradlew and unpack it. arguably even better.. this replaces the existing gradlew as curl https://gradle.com/gradlew | sh and can then use java's internal http client to bootstrap itself. (this could even be a java file with java 11)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[xenoterracide]

still in favor of this

[xenoterracide]

bump, helping someone to get to gradlew on windows and it is like pulling teeth

[RecursiveJoy]

bump pls

[xenoterracide]

lol, bump again, maybe I'll give a go at writing one.

[xenoterracide]

are patches welcome? maybe a Java script to avoid issues with cross-platform shell's

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to to let know so we can reopen the issue. Please try to provide steps to reproduce, a quick explanation of your use case or a high-quality pull request.

[xenoterracide]

I've all but written a version of this myself now. I was going to offer to contribute (again, apparently) but it's obvious the gradle team isn't interested in ease of adoption.

[oleg-nenashev]

@xenoterracide I reopened it based on the feedback and assigned it to you.
It can be a standalone repository, right?

[ov7a]

This is a valid documentation issue.

---

There are no plans to host installation scripts on gradle.org/gradle.com to install gradle with curl | sh. That means we would not accept a PR for that.

The installation guide mentions package managers, although chocolatey (and probably others) should be added for Windows.

[ov7a]

This issue is a good choice for first-time contributors to Gradle, it is actionable and ready for contribution.

See CONTRIBUTING.md for more information.

[xenoterracide]

It can be a standalone repository, right?

yes

This is a valid documentation issue.

There are no plans to host installation scripts on gradle.org/gradle.com to install gradle with curl | sh. That means we would not accept a PR for that.

That fundamentally makes this useless. I assume by not host there you mean you wouldn't support adding it to the doumentation, obviously documentation could easily point to github.com.../script/raw (or whatever order raw is in the url).

mentions package managers, although chocolatey (and probably others) should be added for Windows.

These are a bad idea for gradle, for many reasons. The biggest reason is why you use gradlew itself. It's not a good idea, or probably even functional in many cases to let your package manager use gradle. Unlike yarn 1, to yarn 2, gradle does not delegate to gradlew when present. So it's confusing for users to do this. Installing with a package manager and then removing is the best case scenario right now. Doing it that way though means you get a version of gradlew you might not want, and having to download a full jre that you might not want. Yes, you have to have a jre anyways, but it might not be that one, and any package manager (I've used) will force a jre download when you install gradle.

I've had people walk me through doing it with another already set up repo, I've had people talk about how to do it if you've somehow hosed the gradlew scripts but still have an unhosed jar.