**sigh**
Gradle.

yupp, it's strange sometimes.

@thebiochemic It just never works for me... I haven't had a single project built without spending at least half an hour troubleshooting Gradle.

@Khazbs never got any real issues hmm.. only when project settings were wrong

it's my go-to build tool, rly. Far nicer to work with than Maven

@joewilliams007 @netikras How.....

At this point I'm inclined to try Bazel as a replacement for Gradle

@Khazbs in every way, really.

What's bugging you?

I really like Grafdle still compared to how I used to link libraries manually In Java build config.

@netikras

I maintain a legacy Android+iOS mobile Cordova app, and I have to use Gradle to build the Android app.

There are always problems with it, like Gradle version is not supported in this version of Android Studio, Gradle version doesn't match Android Gradle Plugin version, Gradle cannot find the Android SDK. Sometimes builds just fail for reasons, and when I Google for solutions, I only find old suggestions to downgrade Gradle to now unsupported versions, so usually I have to re-generate the Android app and somehow make it build again.

Now that I look at it, the main problem I have is Gradle's poor backwards compatibility with the outdated frameworks I have to use. For example, it's common for Gradle to not build old Cordova plugins that still have "compile" instead of "implementation" written in their build files, so I have to fork the plugins and update their build files myself.

@netikras On the contrary, when I try to use modern frameworks, like Flutter or Jetpack Compose, for building other apps, Gradle has problems too, but perhaps because these frameworks are still in Beta, so compatibility problems are kind of expected.

Oof

@Khazbs yeah i had that cordova mindfuck a few months ago aswell. It is a pain in the ass to do anything with it.

@Khazbs Sounds to me like your project is messed up. And yes, Gradle + Android is an annoying combo - I can agree with that.

But, since Gradle works flawlessly for me with non-android projects, I'm guessing it's the Android plugin that's bugging you, not Gradle itself.

@Khazbs

Yeah, my main gripe with Gradle is that, at least back when I last did native Android, it seemed like they couldn't settle for the DSL they wanted (in the android plugin at least).

Versions upon versions coming out, making breaking changes to the spec, breaking your builds.

I get that projects require long term maintenance, but I would like not having to fix builds every couple months or anytime a new dev clones the project.

@netikras I think you're right, looks like it's the Android Gradle Plugin that makes me wanna smash my laptop closed and hammer nails into its lid

@Khazbs know the feeling. Causes intrusive thoughts. Love it :)

@netikras do you have any Scala projects running with it................

(not that I want to migrate from SBT, as that would mean a lot of insanity and probably me trying to fuck every day an electric outlet hoping to get electrocuted and be relieved by death)

Gradle sucks so much
Takes like 10s for whatever reason to do the most basic things like showing the list of tasks
Or I had to google and try random shit for half an hour just so it would display logs from tests

@IntrusionCM nope

Don't blame the tools

Blame the users

@snakebyte Sir, this is DevRant, here we blame every thing that comes to mind

Update from everyone's favorite clown

https://msn.com/en-us/news/...