That groovy code is unfixable, it's a known issue. Warning existed since Java
9... We may try to update to later groovy, but it's a known issue and can be
done later. One thing after the other! Just ignore it. For those who follow
Jenkins jobs during the last years, it's well known.
Uwe
Am Apr
Hi again,
I was on my mobile only, so here is the "lengthy" explanation:
> FYI: first oddity i noticed is coming from some groovy code that seems
> to run as part of "common.test" ?
> -check-totals:
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective acces
: > - The HTML linter based on HTML Tidy was disabled until we found a
: > replacement (no HTML 5 support - Java 11 produces HTML5 Javadocs). So it
: > might happen that bad javadocs are not detected in master but after merge
: > to 8.x branch they might suddenly appear.
:
: Maybe we can use the
: The master branch was updated to use Java 11 - all Jenkins Jobs are back
online! Let's see if additional Jenkins failures occur.
FYI: first oddity i noticed is coming from some groovy code that seems
to run as part of "common.test" ?
$ git clean -fx && cd solr/core/ && ant test -Dtestcase=T
Big THANKS to all who worked on this. I just took about 10 minutes to have
everything up and running in IntelliJ, building from the command shell, etc.
Most all of that just waiting for compilations to finish and tests to run….
That was about as painless as I could hope for.
Erick
> On Apr 16,
Hi,
The master branch was updated to use Java 11 - all Jenkins Jobs are back
online! Let's see if additional Jenkins failures occur.
Go ahead and update your local dev environment:
> As discussed on https://issues.apache.org/jira/browse/LUCENE-8738, we are
> planning to switch master branch to
