On Mon, Sep 8, 2025 at 10:59 AM Sergey Chernov <[email protected]> wrote: >
> Google and Meta are not relevant examples, as these companies have their > own build tooling (Bazel/Blaze, Buck/Buck2, immense monorepos etc) which is > not common. Google is a huge Java shop, with thousands of active Java developers, many of whom do use Maven. I was one of them, and at one point they paid me and a team of developers fulltime to make their Maven builds work better. They also use gradle, occasionally bazel, and most often blaze. Maven is probably the number 2 build tool for Java code at Google, after blaze. Meta isn't as big a Java shop as Google, but they also use Maven; e.g. on the Presto project. The numbers you cite from JetBrains show only 67% of developers use SpringBoot. That means a third aren't using SpringBoot, and probably more than half of all active projects (i.e. not just web framework based projects) aren't using SpringBoot at all. Maven should support SpringBoot, but neither require nor assume it. Maven is for all kinds of Java projects, not just for web projects and certainly not just for SpringBoot. -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
