News for hackers. Stuff that matters.
Re:Exodus: Easily migrate your JVM code from Maven to Bazel by nimrody on Wednesday April 07, 2021 @04:34AM (#26721904)
Maven just hides the complexity in its plugins which are implemented in Java.

If you don't need any plugin - then, yes, it's simple.

But once you need specialized plugins it's no better than gradle/bazel. The latter two lets you add some logic in the build scripts - so at least it's visible to users. If you need special functionality in Maven you have to write a plugin or gather a few plugins. And when it breaks down (as all tools do) -- it's difficult to find the code and understand the problems.

Re:Exodus: Easily migrate your JVM code from Maven to Bazel by krzyk on Wednesday April 07, 2021 @04:38AM (#26721938)
Writing Maven plugins is quite easy and doesn't require you to learn another language (like in case of gradle, you have to know groovy).
Re:Exodus: Easily migrate your JVM code from Maven to Bazel by tn1 on Wednesday April 07, 2021 @04:55AM (#26722038)
At least with Groovy, most Java programs are also valid groovy programs (the converse is not true, but not too different).
Re:Exodus: Easily migrate your JVM code from Maven to Bazel by krzyk on Wednesday April 07, 2021 @01:55PM (#26728395)
Yes, but with groovy you get magnitude slower compilation time, less efficient autocomplete.

And a language that has sometimes strange design choices.

Groovy is like PHP, if I need to upgrade from Java it would be Scala. At least I get a superior language for also magnitude slower builds.

Re:Exodus: Easily migrate your JVM code from Maven to Bazel by tn1 on Wednesday April 07, 2021 @07:50PM (#26733156)
Gradle has a Kotlin Script build script option these days too. I haven't tried it yet, so I'm not sure if it's any better.