3 ms·
I originally hated Gradle due to its sheer complexity, but there was an incident that I was put off by Maven. I realized that even with the simplest configurati
by xpressvideoz 3y ago
I originally hated Gradle due to its sheer complexity, but there was an incident that I was put off by Maven. I realized that even with the simplest configuration possible, Maven tried to re-create a `.jar` file on `mvn package` every time even when I didn't change any files. Maven is famous for not utilizing incremental builds well and this shows. The strange thing is that incremental builds in Maven sometimes work. I could not find the rules behind this. These unpredictable behaviors make me nervous when I use Maven. Gradle is extremely complex and its behavior changes between versions, which makes my life harder, but at least at a specific version, Gradle's behavior has been stable. Just my two cents.
- gbear605 3y agoMaven’s added incremental builds as a full feature in recent versions and it seems to work pretty well.
- cogman10 3y agoNice. This is literally the one reason I preferred gradle to maven. For our bigger projects maven simply took too much time.
- richbell 3y agoIncremental builds and test caching (plus that nifty UI) were always two things that made me strongly consider switching to Gradle.