-1 from me. I have a philosophical objection.
Much like HTTP's mod_rewrite[1] gradle's greatest strength is that it
allows the developer to do so much in so many ways. But its greatest
weakness is that it allows the developer to do so much in so many ways.
My experience with Ant and Gradle is that in a fairly short period of time
the build scripts become so complex that it takes a development team just
to maintain them.
The greatest strength of Maven is that it requires developers to seriously
work to do things outside of the "Maven way". But its greatest weakness is
that developers have to seriously work to do things outside of the "Maven
way".
My experience with Maven is that if the developer wants to do something
outside of the "Maven way" it is difficult, but it also forces the
developer to think about what they are doing.
With respect to this project, it is my opinion that we do not want to
create a build system that is so complex that it becomes difficult for the
uninitiated developer to contribute to the project.
If the goal here is to provide a gradle build in parallel with the Maven
build then I would want to have a -1.5 vote. Adding the extra work
associated with keeping the Gralde build sane onto the work associated with
ensuring the 2 builds provide the same output detracts further from the
goal of having a project that most experienced developers can join with
minimal effort.
Not to put too fine a point on it, but I think we want to focus on
developing, supporting and maintaining the software not developing,
supporting, and maintaining a build system to make the software.
Claude
On Fri, Jul 17, 2020 at 12:12 AM Singh, Baljit (GE Aviation, US) <
balsi...@ge.com> wrote:
> +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
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
