On a related note, anyone with non-trivial build needs can always develop Maven plugins to fill in any gaps in a more integrated fashion. That’s what we do in Jenkins, for example, and that’s an incredibly complex ecosystem. You get a ton of freebies with Maven which is fantastic for libraries especially.
In my experience, Gradle was most useful in building standalone applications, though that’s fairly doable with Maven anyways. It’s mostly useful when you have a critical mass of developers who prefer it; otherwise, you end up with only half a person who understands the resulting build scripts. On Sat, Jul 18, 2020 at 08:37 Xeno Amess <xenoam...@gmail.com> wrote: > -1 for me. I have experience of grade about maintaining 5 or 6 gradle > projects, including my graduationg project. > And I think gradle shitty. > > Adam Retter <adam.ret...@googlemail.com.invalid> 于 2020年7月18日周六 下午8:18写道： > > > -1 from me. I have only ever found Gradle to be worse than Maven. > > > > On Thu, 16 Jul 2020, 23:30 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 > > > > > > > > > -- Matt Sicker <boa...@gmail.com>
