Include Gradle Wrapper

[PizzaCrust]

No description provided.

[Techcable]

Why don't we just tell them to install gradle?

[PizzaCrust]

They might have installed an older version of Gradle, or a newer incompatible version. But, with the gradle wrapper; you can control the version.

[phase]

In the README, we could control the gradle version we want them to use. I don't see why this is a big deal, I couldn't tell you the difference between any two gradle versions.

[PizzaCrust]

Really? (gradle differences)

New version:

plugins {
    id 'java'
}

Old version:

apply plugin: 'java'

[phase]

We could just say "use the latest version of Gradle"

[PizzaCrust]

Having to redownload Gradle, manually from the webpage and extracting it; whenever a gradle version comes out is just plain repetitive.

The Gradle Wrapper automates this process.

[phase]

lol use linux pm install gradle

But seriously, we'll probably add a wrapper.

[Techcable]

No one seems to have 'redownloading' issue with maven, so I'm not exactly sure why the wrapper always comes up with gradle.
Honestly I don't foresee needing the wrapper for any reason except to spare windows users a few minutes to run the gradle installer.

[minecrafter]

@Techcable using that logic is naive. The wrapper makes it simple even for those on *nix platforms to build Gradle projects. For one thing, the version of Gradle provided may be too old (think of Debian or RHEL-based systems).