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
I am not going to vote on this, but if people decide to migrate some
projects over to Gradle I would be willing to help with that.
On 2020/07/16 23:30, Rob Tompkins 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
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 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
> Sprin
+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 verbos
> On Jul 16, 2020, at 7:00 PM, Alex Remily wrote:
>
> For those of us not as familiar with Gradle, what are some of the
> benefits? Drawbacks?
So gradle is an analog of maven, in that it provides dependency management in
the same fashion. However, the configuration is written in groovy (no
m: Rob Tompkins
Sent: Thursday, July 16, 2020 8:48 PM
To: Commons Developers List
Subject: Re: [all] Thoughts on build system maven -> gradle??
> On Jul 16, 2020, at 7:00 PM, Alex Remily wrote:
>
> For those of us not as familiar with Gradle, what are some of the
> benefits? Drawba
nt? Is it
> restricting us in some way?
>
Not at all, just trying to gauge community opinion here.
-Rob
> Regards,
> Matt
>
> From: Rob Tompkins
> Sent: Thursday, July 16, 2020 8:48 PM
> To: Commons Developers List
> Subject: Re: [all]
r because how
closely we’re tied to maven. I just wanted to see what people thought.
>
> -Rob
>
>> Regards,
>> Matt
>>
>> From: Rob Tompkins
>> Sent: Thursday, July 16, 2020 8:48 PM
>> To: Commons Developers List
; I’d like to reiterate that, clearly, this all may be a non-starter because
> how closely we’re tied to maven. I just wanted to see what people thought.
>
> >
> > -Rob
> >
> >> Regards,
> >> Matt
> >>
> >> From:
gauge community opinion here.
>>
>> I’d like to reiterate that, clearly, this all may be a non-starter because
>> how closely we’re tied to maven. I just wanted to see what people thought.
>>
>>>
>>> -Rob
>>>
>>>> Regards,
>>&
t;
> > >
> > > Not at all, just trying to gauge community opinion here.
> >
> > I’d like to reiterate that, clearly, this all may be a non-starter
> because
> > how closely we’re tied to maven. I just wanted to see what people
> thought.
> >
> >
-0.5 from me, to have suffered from projects having done it I think it
wouldn't be sane for commons
Big advantage of gradle is to be flexible but it also means you do a one
man build, lose most of the IDE integration (even IDEA integration is not
good, you often must use gradle runner to run test c
-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 t
On 17.07.20 10:13, Claude Warren wrote:
> -1 from me. I have a philosophical objection.
Same here: -1
> 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 s
Very much appreciation guys for the thoughtful words and opinions here. Sounds
like we’re sticking with Maven. :-)
I hope everyone is doing well these days.
Cheers,
-Rob
> On Jul 17, 2020, at 4:24 AM, Thomas Vandahl wrote:
>
> On 17.07.20 10:13, Claude Warren wrote:
>> -1 from me. I have a
Hi Rob,
Even though I am on the minus side, I am glad you brought this up for
discussion. I think it helped us better understand where we are, how we got
here, and why we want to stay.
Gary
On Fri, Jul 17, 2020 at 7:25 AM Rob Tompkins wrote:
> Very much appreciation guys for the thoughtful wor
I agree with Gary. I know its been decided but I thought I would add
my -1.
Technology better have a compelling reason to switch and in the past we
have had:
Ant -> Maven was a big leap for convention over configuration and
dependency management
SVN -> GIT was a big leap for the handling
-1 from me. I have only ever found Gradle to be worse than Maven.
On Thu, 16 Jul 2020, 23:30 Rob Tompkins, 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
-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 于 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, wrot
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
espe
-1, I'd rather return to Ant than switching to Gradle.
Gradle builds quickly become messy as hell, if you compare several
Gradle based projects like Hibernate, Spring and OpenJFX they hardly
look similar. Maven POM files may look verbose but at least the
declarative syntax enforces a normalized pr
21 matches
Mail list logo