I know little about gradle and have only just started exploring it, so this is just a question out of curiosity.

It’s supposedly a language agnostic dependency manager and builder, yet it seems to have only found its niche in Java. C/C++ projects could definitely do with dependency resolution…

  • Quetzalcutlass@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 days ago

    Gradle is so insanely over-engineered that it can do almost anything, yet so fragile that it can take weeks of bashing your head against the wall to get your build scripts working if you’re doing anything remotely complicated with your setup (or even just upgrading Gradle versions). Everything is so finicky that even if you do things exactly as the documentation says, you’ll still have to finagle things around nine times out of ten to get it to compile.

    The user guide is longer than some novels.

    • tyler@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      23 hours ago

      Gradle upgrades are dead simple… like yeah I get a bunch of the other criticisms of Gradle, but they mark things as deprecated two full major versions ahead and then slowly phase them out. Upgrades are a single command.

      I haven’t really encountered the issues others are having and I’m guessing a lot of them occurred before Gradle’s switch to kotlin.

      Edit: or the issues are actually from android build tool and not actually Gradle