; > -Original Message-
> > From: Erick Erickson
> > Sent: Thursday, August 27, 2020 11:11 PM
> > To: dev@lucene.apache.org
> > Subject: Re: Current workflow for steps before commiting changes
> >
> > Alexandre:
> >
> > "./g
://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Erick Erickson
> Sent: Thursday, August 27, 2020 11:11 PM
> To: dev@lucene.apache.org
> Subject: Re: Current workflow for steps before commiting changes
>
> Alexandre:
>
> "./gradlew c
Alexandre:
"./gradlew check” is all you need. That does what “ant precommit test” would do.
Dawid put some pretty great help in, "./gradlew help” shows the top-level help
tasks, and “./gradlew helpAnt” gives some very useful gradle versions of some
of the familiar Ant targets you’re used to.
Hello,
So, what's the current post-changes pre-commit workflow for master (9)?
Do I run gradlew precommit? Does that include actual tests or need
those separately? Do I need to run ant precommit as well?
I am mostly removing things, but need to make sure no dangling
references will cause