Why I Moved Back from Gradle to Maven

Post by dcposch » Wed, Apr 04, 2018, 3:23 AM UTC

Post by gleenn » Wed, Apr 04, 2018, 3:35 AM UTC

lokedhs wrote: post #91

tsvetkov wrote: post #41

Earlier quoted context omitted.

I think it's not correct to say that Turing-completeness somehow prevents extracting project structure. If a build tool can extract that information, why IDE could not do that? In fact this is how Gradle projects are imported into Intellij and Eclipse: Gradle builds project model by running Groovy or Kotlin scripts, and then IDEs are working with declarative model. The real problem is working with scripts themselves:…

To answer your question as to why an IDE can't do it, the reason is that in order to do it you need to solve the halting problem. Of course, the IDE can do it if you limit yourself to a subset that is not fully Turing complete, which is what IDEA does today. The issue a lot of people have with Gradle is that this subset is not well defined, and it's very easy to do something that works but will get the tools to have…

Post by tenken » Wed, Apr 04, 2018, 4:41 AM UTC

lmilcin wrote: post #53

bitcharmer wrote: post #48

Earlier quoted context omitted.

I'm neither Maven nor Gradle ninja. Just a senior software developer with 15+ years of experience... > Maven requires a lot of boilerplate for everything. Copy-paste I think you may be doing it wrong. Maven supports declaring project-wide or module-wide entities and their attributes at every level. Duplication or copy-paste is a sign of not understanding Maven > Gradle... It's an environment for programmer To me this…

It may be you are doing plain simple (can be large, but still simple) projects for which Maven is perfectly fine. Gradle is for when you require some more complicated behaviour in your project. For example in my current project the applications are packaged into completely custom and proprietary package that is then being used by the completely custom automation to be deployed to the infrastructure. I have created a…

Post by Yeroc » Wed, Apr 04, 2018, 4:47 AM UTC

kodablah wrote: post #57

bborud wrote: post #32

Flexibility is not something I want in a build system. I want predictability and simplicity. "Flexibility" just means that the dumbest guy on the project will find sufficient rope to hang the whole team sooner or later. That being said, "flexibility" is not special to Gradle. As long as there have been build systems there have been people who are too lazy to learn them and get "bright ideas". For instance I have no i…

> Flexibility is not something I want in a build system. [...] "Flexibility" just means that the dumbest guy on the project will find sufficient rope to hang the whole team sooner or later. We're on opposite sides here. I can control my team wrt rope and what not. But it's very hard to wrangle a build system to perform some advanced task you need without flexibility. I'd way rather have problems with the build system…

Post by pjmlp » Wed, Apr 04, 2018, 4:57 AM UTC

dljsjr wrote: post #23

bsder wrote: post #17

Earlier quoted context omitted.

Fix the documentation! Focus on Android Studio because that's the only place people really use Gradle because they are forced to do so. You need to create a LOT of Android Studio sample projects, and they need to be kept up to date for the various versions of Android Studio. If you did nothing but create "Hello World" in a zillion various flavors (Java, Kotlin, Scala, NDK, NDK with static library on different archite…

Please don't say that nobody uses Gradle outside of Android devs. We're a shop that definitely does zero Android development and we still use Gradle, the fact that people assume Gradle Anroid Dev is already a huge pain point for us when we start looking for third party educational resources.