while I broadly feel that gradle is the superior choice and would never go back, I do have to agree that the backwards incompatible changes made to the engine can be frustrating. the general bugginess of releases is also astounding for a project with such widely promoted usage. just last week I encountered some sort of edge case where every (nominally 15s) build I ran took about 5s longer, up until it was well over a minute. upgraded to the latest release and it went away. pretty rough for a project so intensely pushed by GOOG.
When I was developing Java I despised Maven with all the copy-pasta oriented project files, and I thought its process was overly complicated.
Now, when working on .Net Core projects I still have to manually edit, and copy paste build file fragments to the .csproj files (this is greatly because of bugs in Visual Studio’s related features), but what I see is that Maven had some great features, which are missing from other build tools.
I don’t know much about Gradle, but I suspect has roughly the same feature set as maven. What I really miss in other build tools is the Maven Bill Of Materials feature. When working with several projects made up of many shared components (libraries) this approach helps versioning and ensuring compatibility and interoperation so much, I could not appreciate when I was there.
I came from a gradle company to a maven company and the amount of support-wrapper-scripts and duct-tape around maven here is crazy. Maven says that all builds are the same, except that they are not. Gradle would be so much better here, but I have other things to focus on right now…
while I broadly feel that gradle is the superior choice and would never go back, I do have to agree that the backwards incompatible changes made to the engine can be frustrating. the general bugginess of releases is also astounding for a project with such widely promoted usage. just last week I encountered some sort of edge case where every (nominally 15s) build I ran took about 5s longer, up until it was well over a minute. upgraded to the latest release and it went away. pretty rough for a project so intensely pushed by GOOG.
When I was developing Java I despised Maven with all the copy-pasta oriented project files, and I thought its process was overly complicated.
Now, when working on .Net Core projects I still have to manually edit, and copy paste build file fragments to the
.csprojfiles (this is greatly because of bugs in Visual Studio’s related features), but what I see is that Maven had some great features, which are missing from other build tools.I don’t know much about Gradle, but I suspect has roughly the same feature set as maven. What I really miss in other build tools is the Maven Bill Of Materials feature. When working with several projects made up of many shared components (libraries) this approach helps versioning and ensuring compatibility and interoperation so much, I could not appreciate when I was there.
I came from a gradle company to a maven company and the amount of support-wrapper-scripts and duct-tape around maven here is crazy. Maven says that all builds are the same, except that they are not. Gradle would be so much better here, but I have other things to focus on right now…