I think the gradle-master branch is already workable enough to land on master.
If you're not familiar with gradle then, once merged, run "gradlew help". Some notes. 1) I have been running tests on Windows and Linux, they're ok. The output is slightly different from ANT's but I think it's fine for working. 2) The speed of compilation and running tests selectively is much better than ant's, especially on multicore machines. 3) I use IntelliJ idea and the project imports into the IDE without any special handling. Code formatting and such may need to be adjusted though. 4) Some things are incomplete (precommit does a subset of checks). Some are missing (regeneration tasks). Some are different (handling of dependencies, build output folder locations). It will take some time and learning to live with a new build system. I tried to provide short guides into selective areas (they're available as help tasks or plain text files under help/). 5) If something does *not* work, let me know. 6) It'd be nice if we had a build job somewhere on a faster machine that would run at least "gradlew precommit check -x test" so that rudimentary checks are applied, without running all the tests. This would ensure consistency in dependencies, for example. 7) The parallel branch (gradle-master) and issue (LUCENE-9077) will be kept open and occasionally merged back and forth. I have to shift more focus to my daily job but will help out and chip at the remaining bits, time permitting. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
