Thanks for the input Volkan!

> By switching to another build tool (Bazel or anything else), I expect to
> speed up these processes, maybe, by having more fine-grained control on the
> dependency graph and avoiding unnecessary steps.
>

I see quite often people switching from Maven to Gradle because Gradle
gives some flexibility on customizing the build cycle
and also because some people find it more convenient to use a scripting
language (rather than XML) to define the build process.
It seems to be a positive point in favor of Gradle when it comes to fine
tuning the build.

Still, I'm curious about the use of Gradle in a monorepo.
Is there some particular reason to think that Gradle is not a good fit for
Log4J?

About keeping Maven, wouldn't it be an alternative to use Build Profiles
[1] to skip unnecessary tasks?

If others want to share some thoughts on the topic, it would be good too.
Maybe, that's something that I can do some investigation and contribute to
the community.

[1]
https://maven.apache.org/guides/introduction/introduction-to-profiles.html

Best,
Jeanderson Candido

Reply via email to