3 ms·

Then they fked up big time with the config file. Gradle has a correct view of the build graph, unlike maven. There are never a case (unless deliberately broken

• iainmerrick 3y ago
  "Deliberately" is a rather strong way to say "accidentally". When multiple different totally independent teams manage to subtly break things, I think you have to start questioning the tool rather than the teams. Like, I don't know, maybe the problem was caused by a dependency they were using rather than their own build scripts. How do you know, how do you fix it? What are you supposed to do, not use dependencies?
  • kaba0 3y ago
    A gradle dependency is a finished artifact. It gets added to the classpath, what could it break? A gradle plugin could potentially break something, but a) you ain’t writing gradle plugins willy-nilly, b) if it’s a “big” one, it’s likely not gonna be that bad.