4 ms·

Strange, gradle is just way faster in my use cases. Maven has always been a pain with regards to speed with handling dependencies.

Jakobeha 6y ago
Yeah, this article is really not convincing. I've used both gradle and maven and IMO gradle is better in practically every way.
- jimbob45 6y ago
  Is there a benefit to using either over MSBuild?
  - mobilio 6y ago
    Or Make? CMake?
  - escardin 6y ago
    I assume if you are using MSBuild you're building .net or otherwise using visual studio. If you want to build these projects with gradle or maven you still have to invoke MSBuild in my experience. It's not strictly necessary AFAIK, but you'd be giving up a lot of what visual studio offers you for little in return. In general, if you aren't already using a JVM language, there is not a whole lot of reason to use maven or gradle. Pretty much every language has equivalent native build tooling that you should be using instead. If you are using a JVM language, even for part of your build process, then both can be used as the primary build tool and invoke the build tooling of the other ecosystems as needed. This is most useful when you have a native component that you are using from the JVM. I have in the past used gradle to build the native C++ components for apps, but in general it reached out to msbuild on windows, and make files on linux. I've used gradle it to invoke npm commands to build the frontend component of a WAR java webapp.
johnisgood 6y ago
If Gradle is fast in comparison to Maven, then I cannot begin to imagine how slow Maven is. A build system that has to spawn a daemon to speed up the process is a pretty shitty one. It takes about 2-3 minutes to do that for me, and still it takes 30 seconds to build my program which is not even that huge.
- elygre 6y ago
  Are you saying that it takes 2-3 minutes to start the grade daemon? That sounds weird.
  - johnisgood 6y ago
    Yeah, it does. I have 8 GB memory, and an Intel G3xxx CPU. I am baffled by how slow it is. For people who do not believe me, I am willing to record it, but I have to go to sleep now. :/
    - antonyh 6y ago
      That's been my experience of Gradle too. It's always been slower than Maven for me. In any case, 90% of build time is unit tests for the projects I've worked on, so switching tools offer minimal benefit in that regard.
- winrid 6y ago
  Something is wrong with your setup methinks. Gradle daemon starts in a second or so for me on the two Java projects on this machine (around 20koc each) and like one second build times...
  - johnisgood 6y ago
    What could possibly be wrong with the setup though that would cause it? I have a couple of dependencies, including libGDX, artemis-odb, and kotlin-stdlib-jdk8. I posted it in another comment, but I am willing to record it when my time allows. It is quite baffling. I never encountered such slow compilation times even though I compiled some C++ projects before.
throwaway189262 6y ago
There's a maven daemon project now that closes most of the speed gap for my projects

Jakobeha 6y ago

Yeah, this article is really not convincing. I've used both gradle and maven and IMO gradle is better in practically every way.

jimbob45 6y ago
Is there a benefit to using either over MSBuild?
- mobilio 6y ago
  Or Make? CMake?
- escardin 6y ago
  I assume if you are using MSBuild you're building .net or otherwise using visual studio. If you want to build these projects with gradle or maven you still have to invoke MSBuild in my experience. It's not strictly necessary AFAIK, but you'd be giving up a lot of what visual studio offers you for little in return. In general, if you aren't already using a JVM language, there is not a whole lot of reason to use maven or gradle. Pretty much every language has equivalent native build tooling that you should be using instead. If you are using a JVM language, even for part of your build process, then both can be used as the primary build tool and invoke the build tooling of the other ecosystems as needed. This is most useful when you have a native component that you are using from the JVM. I have in the past used gradle to build the native C++ components for apps, but in general it reached out to msbuild on windows, and make files on linux. I've used gradle it to invoke npm commands to build the frontend component of a WAR java webapp.

johnisgood 6y ago

If Gradle is fast in comparison to Maven, then I cannot begin to imagine how slow Maven is. A build system that has to spawn a daemon to speed up the process is a pretty shitty one. It takes about 2-3 minutes to do that for me, and still it takes 30 seconds to build my program which is not even that huge.

elygre 6y ago
Are you saying that it takes 2-3 minutes to start the grade daemon? That sounds weird.
- johnisgood 6y ago
  Yeah, it does. I have 8 GB memory, and an Intel G3xxx CPU. I am baffled by how slow it is. For people who do not believe me, I am willing to record it, but I have to go to sleep now. :/
  - antonyh 6y ago
    That's been my experience of Gradle too. It's always been slower than Maven for me. In any case, 90% of build time is unit tests for the projects I've worked on, so switching tools offer minimal benefit in that regard.
winrid 6y ago
Something is wrong with your setup methinks. Gradle daemon starts in a second or so for me on the two Java projects on this machine (around 20koc each) and like one second build times...
- johnisgood 6y ago
  What could possibly be wrong with the setup though that would cause it? I have a couple of dependencies, including libGDX, artemis-odb, and kotlin-stdlib-jdk8. I posted it in another comment, but I am willing to record it when my time allows. It is quite baffling. I never encountered such slow compilation times even though I compiled some C++ projects before.

throwaway189262 6y ago

There's a maven daemon project now that closes most of the speed gap for my projects