4 ms·
I find that little hurdle actually improves the quality a lot. It means people don't write maven plugins for every single conceivable scenario; usually there wi
by lmm 6y ago
I find that little hurdle actually improves the quality a lot. It means people don't write maven plugins for every single conceivable scenario; usually there will be at most one or two plugins for whatever you wanted to do, properly documented and maintained, whereas with gradle there will be four or five different plugins with no documentation each of which only covers half of the task. And forcing people to put logic in actual released plugins rather than ad-hoc one-liners in the middle of the build definition means you avoid ending up with a bunch of ad-hoc one-liners scattered throughout your build definition, which is much better for long-term maintenance.
- dmitryminkovsky 6y agoYeah for sure, and that's what makes Maven a great tool at the end of the day. It's just those instances you encounter rarely where existing Maven plugins are not enough that I've wished I was using Gradle so I could drop a few one-liners and be done with it. I really like Groovy so any excuse to write some Groovy is always tempting. As you say, a few one liners here and a few one liners there can make a build incomprehensible. So people need to recognize that and keep their Gradle builds approachable if they're going to be doing that. It's pros and cons.