+1 from me. I prefer Gradle for two main reasons:
- Control over how a library's dependencies are exposed ("api" vs
"implementation", see
https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_configurations_graph)
- build.gradle is a lot simpler and a lot less verbose than pom.xml
Drawback: Maven probably has a lot more plugins.
On 7/16/20, 7:00 PM, "Alex Remily" <alex.rem...@gmail.com> wrote:
For those of us not as familiar with Gradle, what are some of the
benefits? Drawbacks?
On Thu, Jul 16, 2020 at 5:30 PM Rob Tompkins <chtom...@gmail.com> wrote:
>
> I think we might be coming towards time to make this move or at least
accommodate for gradle builds in commons. Let’s look to the success the Spring
Framework has had here with gradle. That said, I’m merely trying to gauge
opinions here and am entirely content to stay with maven, if that’s what the
community wishes.
>
> I’m a +1 on at least letting gradle be a part of our systems (don’t have
to get rid of maven either).
>
> Cheers,
> -Rob
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
