Hi,

> > On a side note, the Lucene codebase still uses the deprecated (as of
> > JDK17) AccessController
> > in the RamUsageEstimator class.
> > We suppressed the warning for now (based on recommendations
> > <http://mail-archives.apache.org/mod_mbox/db-derby-
> >
> dev/202106.mbox/%3CJIRA.13369440.1617476525000.615331.16239514800
> > 5...@atlassian.jira%3E>
> > from the Apache Derby mailing list).
> 
> This should not be an issue, because we compile Lucene with javac parameter
> "--release 11", so it won't show any warning that you need to suppress. Looks
> like your build system at Amazon is not the original one by Lucene's Gradle,
> which shows no warnings at all.

Do you get this error in lucene:core:ecjLintMain and not during compile? Then 
this is https://issues.apache.org/jira/browse/LUCENE-10185, solved already. 
This problem did not happen in Lucene builds because we run Gradle with JDK 11 
(JAVA_HOME) and only compile with JDK 17 (passed as RUNTIME_JAVA_HOME).

Uwe

> Uwe
> 
> > Gautam Worah.
> >
> >
> > On Mon, Oct 18, 2021 at 3:02 PM Michael McCandless <
> > luc...@mikemccandless.com> wrote:
> >
> > > Also, I try to semi-aggressively upgrade Lucene's nightly benchmarks to 
> > > new
> > > JDK releases and leave an annotation on the nightly charts:
> > > https://home.apache.org/~mikemccand/lucenebench/
> > >
> > > I just now upgraded to JDK 17 and kicked off a new benchmark run ... in a
> > > few hours it should show the new data points and then I'll try to remember
> > > to annotate it tomorrow.
> > >
> > > So let's see whether nightly benchmarks uncover any performance changes
> > > from JDK17 :)
> > >
> > > Mike McCandless
> > >
> > > http://blog.mikemccandless.com
> > >
> > >
> > > On Mon, Oct 18, 2021 at 5:36 PM Robert Muir <rcm...@gmail.com> wrote:
> > >
> > > > We test different releases on different platforms (e.g. Linux, Windows,
> > > > Mac).
> > > > We also test EA (Early Access) releases of openjdk versions during the
> > > > development process.
> > > > This finds bugs before they get released.
> > > >
> > > > More information about versions/EA testing: https://jenkins.thetaphi.de/
> > > >
> > > > On Mon, Oct 18, 2021 at 5:33 PM Kevin Rosendahl
> > > > <kevindrosend...@gmail.com> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > We are using Lucene 8 and planning to upgrade from Java 11 to Java 17.
> > > We
> > > > > are curious:
> > > > >
> > > > >    - How lucene is testing against java versions. Are there 
> > > > > correctness
> > > > and
> > > > >    performance tests using java 17?
> > > > >       - Additionally, besides Java 17, how are new Java releases
> > > tested?
> > > > >    - Are there any other orgs using Java 17 with Lucene?
> > > > >    - Any other considerations we should be aware of?
> > > > >
> > > > >
> > > > > Best,
> > > > > Kevin Rosendahl
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > > >
> > > >
> > >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Reply via email to