Stack vs Cabal was a huge argument where I worked with multiple teams using different build tools. Add Nix and nix2whatever, and it was more fun. Spent half my time debugging build instructions
I haven't had that experience for newer code bases. Yes, there's some ancient "works only in my IDE" stuff but that's really not how modern Java is written.
Yes, there is a disagreement about whether to use maven or gradle, but IMHO they both work reasonably well out of the box.
Yes. I've been in teams where there has been gradle vs maven arguments.
Right now the Mac (M1 or M2) users in our team can't run our integration tests. It has been suggested that if we migrate our 50-100 services to Java 17 then the tests will work for them again. Trying to do this breaks the Gradle scripts, and the errors are so vague I can't tell why it's complaining.
pastage|2 years ago
Tainnor|2 years ago
Yes, there is a disagreement about whether to use maven or gradle, but IMHO they both work reasonably well out of the box.
mrkeen|2 years ago
Right now the Mac (M1 or M2) users in our team can't run our integration tests. It has been suggested that if we migrate our 50-100 services to Java 17 then the tests will work for them again. Trying to do this breaks the Gradle scripts, and the errors are so vague I can't tell why it's complaining.