Would there be any interest in a PR that ports spark to gradle?
imrichardcole
All 12 comments
Are there any benefits?
tipsy
on 19 Jun 2016
I believe that's subjective.
The reason I suggested it was because I'm beginning to hack Spark and haven't used maven in several years. I'm now far more proficient and comfortable with Gradle but am aware that doesn't mean everyone will like it.
imrichardcole
on 21 Jun 2016
+1 ... Completely agree with the sentiment of @imrichardcole. Gradle versus Maven is up there with number of stars/watchers/contributors when selecting between projects for me. Unfortunately, I also cannot think of a more objective argument, maybe one can be found in: http://gradle.org/maven_vs_gradle/.
jpe42
on 21 Jun 2016
I'm more than happy to just do it, submit a PR and people can decide for themselves.
imrichardcole
on 21 Jun 2016
Do you think switching to Gradle would make it easier for people to contribute to the project? My understanding is that most people learn Maven before Gradle. Also, our Maven config pretty is minimal, and most people won't really touch it when working on the source code.
tipsy
on 21 Jun 2016
It is always a nightmare for me to get a maven project to work in my eclipse. In comparison with the gradle eclipse plugin, just run gradle eclipse from the command line and everything just works and I don't need to add any plugins to eclipse.
I suspect most maven users have never really used gradle, where as most gradle users have used maven and hope they never have to again.
jpe42
on 21 Jun 2016
Also, if you properly use the Gradle wrapper it will automatically handle installing gradle for the user on any platform.
jpe42
on 21 Jun 2016
I'm the opposite. I've used gradle, and have to use it at work, and desperately wish I never had to touch gradle again for anything. Not saying maven is awesome, but at least you get xml schema validation for your build scripts.
jkwatson
on 21 Jun 2016
@jamespedwards42 gradle wrapper and IDE integration (Intellij) is a big plus for me as well. @tipsy in my case yes, I checked spark out hoping to make a change and then realised it was maven, then I realised I didn't have maven installed, then I broke out in cold sweats about having to install it, set random ENV variables until it worked etc etc.
Again, I'm not naive enough to think that someone coming from a maven background wouldn't feel the same way about gradle. My fork is almost ready, so should have something for people to take for a spin shortly.
imrichardcole
on 21 Jun 2016
OT:
Also, if you properly use the Gradle wrapper it will automatically handle installing gradle for the user on any platform.
There are also maven wrapper projects out there. I prefer this one and usually install it through the embedded maven installation that comes with IntelliJ.
thomaseizinger
on 13 Aug 2016
@jkwatson not sure what exactly brings XML schema validation in Maven; if there's some syntax (or other) error in gradle build script, it'll show some sane error message, there are no real problems with that.
sp-1234
on 3 Oct 2016
Doesn't seem like a lot of people want this.
tipsy
on 19 Feb 2017
Related issues
jsnoriegam
路
6Comments
skyghis
路
3Comments
cnmade
路
6Comments
N0odlez
路
4Comments
Blok5
路
5Comments
Most helpful comment
I'm the opposite. I've used gradle, and have to use it at work, and desperately wish I never had to touch gradle again for anything. Not saying maven is awesome, but at least you get xml schema validation for your build scripts.