Hacker News new | ask | show | jobs
by ap22213 4896 days ago
It's a trade-off, right? As most things in software are.

Recently, I inherited a project that had 10,000s of lines of ant scripts. Resource constrained, I didn't have anyone to maintain that build process. So, I took a few hours and converted those projects to several hundred lines of maven 'scripts'. Now, it works way better than the previous system, because now I can have a person focused on coding features, rather than maintaining process.

Maven was what I knew at the time; and, it fit well enough. Maybe Grails is the right answer, though. Or, something else.

Anyway, ultimately, it comes down to what trade-offs we make and what things we prioritize with our limited knowledge that we have available. And, that is the art of software development.

2 comments

> maybe grails is the right answer

The poster probably means gradle. I am not pointing this out to be pedantic, but because it's not a given that every reader will know their way around the universe of build tools.

Oops - typo. Yeah what he said
Gradle doesn't have the library of plugins Maven has.

Do you really need stupidly concise code in a build process that gets updated .01% of the time compared to the rest of a project? I'd rather have the verbosity and formality (Maven plugin vs. customized groovy)