search

FountainMC / FountainCommon

Common code shared between all implementations
MIT License
1 stars 1 forks source link

Include Gradle Wrapper #1

Open PizzaCrust opened 8 years ago

Techcable commented 8 years ago

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

PizzaCrust commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

Really? (gradle differences)

New version:

plugins {
    id 'java'
}

Old version:

apply plugin: 'java'
phase commented 8 years ago

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

PizzaCrust commented 8 years ago

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 commented 8 years ago

lol use linux pm install gradle

But seriously, we'll probably add a wrapper.

Techcable commented 8 years ago

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 commented 8 years ago

@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).