Thread: Build Automation Tools

Originally Posted by George

Java and kotlin, and me liking maven over gradle is totally a preference thing.

Probably. I started with gradle so it's > imo (+ the benefits ofc )

Originally Posted by Kiissmyswagb

There are no problems with Gradle on Intellij so I'm calling cap. What problems are you talking about?

There are many problems. Gradle not finding the defined dependencies or local subprojects, Intellij randomly showing errors everywhere at project startup, Gradle not using the defined Java version and there are many more. These things happen randomly.

Originally Posted by Displee

There are many problems. Gradle not finding the defined dependencies or local subprojects, Intellij randomly showing errors everywhere at project startup, Gradle not using the defined Java version and there are many more. These things happen randomly.

I haven't had any of those problems after configuring correctly.
In my experience, I had a lot of small issues break some large scale things. When you're working with a monolith project, like most of the community , that can be annoying. I almost ragequit when I was trying to figure out how to publish last year lol.

I really want a mixture of Gradle and Maven tbh. I'm not a particular fan of either.

Maven's fixed lifecycle-based approach to projects holds it back - for example, if you use the exec plugin to make it so you can run your project from the CLI (like `./gradlew run`), you can't make it depend on the compile phase. Its multi-module support is also a bit rubbish. Gradle is much more flexible here as it represents the build as a set of tasks with a proper DAG, including the appropriate dependencies across modules if you run Gradle inside a module.

However, Gradle's DSL is really poor imo - it's inconsistent, and probably too flexible cos you can make a real mess out of your build.gradle file quite easily. Gradle itself is also quite bloated (the fact you need to run the daemon process to avoid having to wait ages for it to start up says it all). Though I suppose one good thing is it does support stuff like parallel/incremental compilation better than Maven does.

I really want something with the best bits from both tools: a more rigid convention-based configuration format or DSL (with more complicated logic in plugins) but with a proper DAG for executing tasks.

Originally Posted by Graham

I really want a mixture of Gradle and Maven tbh. I'm not a particular fan of either.

Maven's fixed lifecycle-based approach to projects holds it back - for example, if you use the exec plugin to make it so you can run your project from the CLI (like `./gradlew run`), you can't make it depend on the compile phase. Its multi-module support is also a bit rubbish. Gradle is much more flexible here as it represents the build as a set of tasks with a proper DAG, including the appropriate dependencies across modules.

However, Gradle's DSL is really poor imo - it's inconsistent, and probably too flexible cos you can make a real mess out of your build.gradle file quite easily. Gradle itself is also quite bloated (the fact you need to run the daemon process to avoid having to wait ages for it to start up says it all). Though I suppose one good thing is it does support stuff like parallel/incremental compilation better than Maven does.

I really want something with the best bits from both tools: a more rigid convention-based configuration format or DSL (with more complicated logic in plugins) but with a proper DAG for executing tasks.

* emphasis on the parts that give me headaches *

Gradle with the [Only registered and activated users can see links. ] is my go to at this point - I haven't used anything which I enjoyed more.
Although publishing still confuses me at times .

Originally Posted by JayArrowz

You could be using it wrong? You might not be committing everything required, you do commit the wrapper
[Only registered and activated users can see links. ]

As for the java version it depends on your gradle configuration.

You probably didn't read my previous posts? I'm not experiencing most of these issues, but I come across many of them when on other peoples PC's.

Originally Posted by Tyluur

I haven't had any of those problems after configuring correctly.
In my experience, I had a lot of small issues break some large scale things. When you're working with a monolith project, like most of the community , that can be annoying. I almost ragequit when I was trying to figure out how to publish last year lol.

Originally Posted by Kiissmyswagb

You're using Grade wrong and you're using IntelliJ incorrectly. These are beginner issues which with experience you'll understand.

Don't be offended by this comment.

I been using Gradle since 2018. I very well know what I'm talking about and doing. I've used Android Studio for over a year. I know what a hell Gradle can be.

I can openup a Gradle project right now in Intellij and get 100 syntax errors for whatever reason. They are just not completly stable together.