I tried it out just to see, here was my experience:

$ git checkout gradle-master
Switched to branch 'gradle-master'
Your branch is up to date with 'origin/gradle-master'.
$ ./gradlew help
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* Where:
Settings file
'/Users/rob.muir/eclipse.workspace/lucene-solr/settings.gradle'

* What went wrong:
Could not compile settings file
'/Users/rob.muir/eclipse.workspace/lucene-solr/settings.gradle'.
> startup failed:
  General error during semantic analysis: Unsupported class file major
version 57

  java.lang.IllegalArgumentException: Unsupported class file major version
57
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:184)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:166)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:152)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:273)
        at
org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:81)
        at
org.codehaus.groovy.control.ClassNodeResolver.findDecompiled(ClassNodeResolver.java:254)
        at
org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:192)

On Wed, Jan 8, 2020 at 9:30 AM Dawid Weiss <[email protected]> wrote:

> 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]
>
>

Reply via email to