On the onboarding new contributors I can definitely say that I agree with
the earlier comment about 'getting surprised to see ant' (having worked on
Maven and Gradle for the last 10+ years). Also, I would recount a specific
challenge I had with making the 'examples' folder as a sub-module in
Intell
I can’t why there would be any objection to adding a guardrail. I think this is
a good idea.
MikeA
"I see this as a task for a follow-up ticket so long as the CEP’s contributors
would not oppose the addition of such a guardrail."
> On 3 Feb 2022, at 16:06, C. Scott Andreas wrote:
>
> I see t
+1
If we can get a pros/cons list we can have a ranked choice vote, move forwards,
and maybe agree not to revisit this for a few years at least?
From: Joshua McKenzie
Date: Thursday, 3 February 2022 at 13:59
To: dev
Subject: Re: Build tool
Could someone take on clearly enumerating the pros an
Could someone take on clearly enumerating the pros and cons of ant vs.
maven?
Without clarity this is going to keep stagnating as a war of
unsubstantiated opinions and fizzle out like it has so many times in the
past.
I'd like to see it either change or the topic be put to rest. :)
On Thu, Feb
On Thu, Feb 3, 2022 at 7:19 AM bened...@apache.org wrote:
> It pretends to be Maven for dependency management, but this is a small part
> of the job of a build file.
It doesn't pretend, it actually uses part of the Maven project to
accomplish its goals. It's half the Maven it could be.
I have been in the guts of build.xml probably a lot more than you realise.
It pretends to be Maven for dependency management, but this is a small part of
the job of a build file.
From: Brandon Williams
Date: Thursday, 3 February 2022 at 13:07
To: dev
Subject: Re: Build tool
On Thu, Feb 3, 202
On Thu, Feb 3, 2022 at 3:23 AM bened...@apache.org wrote:
> If we’re struggling to actually use ant how we want that’s another matter,
> but it’s easy to forget how much just works for us with ant
If you don't regularly work on the build system, it may be easy to
forget that ant works by actual
> I took a massive productivity hit when In-JVM dtests landed the codebase
These introduced new capabilities that were well understood as outcomes at the
time. Here we are proposing replacing something that works fine, with something
that works equivalently.
The build file is not only consumed
> I am productive today with ant. I will almost certainly take a
productivity hit sometime during and after the migration to maven, as will
others.
I took a massive productivity hit when In-JVM dtests landed the codebase,
but this was not a consideration when that framework was added because it
wa
> Aleksei has proven that he was able to deliver work of quality and to push
> things forward. He is willing to try to tackle that work.
I am not questioning his ability to deliver, I am questioning the value of
burdening the project with this migration?
I am productive today with ant. I will a
>
> I don’t have a super strong desire to stay with ant, I just have a desire
> not to unduly burden the project with unnecessary churn. Tooling changes
> can be quite painful.
Aleksei has proven that he was able to deliver work of quality and to push
things forward. He is willing to try to tackl
I think that it is not only about the build tool as such. There is a
lot of scripting involved in build scripts as well as in Jenkins
pipeline and so on. I am not sure how to make a transition like this,
testing it all while people are developing at the same time. Some
problems like parallelisation
I don’t have a super strong desire to stay with ant, I just have a desire not
to unduly burden the project with unnecessary churn. Tooling changes can be
quite painful.
With regards to contributions, this is often brought up but the reality is the
project has always struggled to bring in new on
I think that there are 2 main issues (Aleksei can correct me):
* ANT is pretty old and a lot of newcomers are unfamiliar with it and
surprised by it. By consequence, it might slow down the on-boarding of
newcomers which we want to make as smooth as possible.
* Aleksei has been working on migrating
I’m going to be a killjoy and once again query what value changing build system
brings, that outweighs the disruption to current long-term contributors that
can easily get things done today?
At the very least there should be a ranked choice vote that includes today’s
build system.
From: Maulin
Thanks for opening that discussion Aleksei.
I am also in favor of Maven. My previous experience with Graddle was not
great.
Le jeu. 3 févr. 2022 à 08:45, Berenguer Blasi a
écrit :
> Hi All,
>
> I've had a similar experience. Gradle is super powerful but suddenly it
> becomes one more 'thing' on
16 matches
Mail list logo
