The OWASP one succeeded. I updated some other "main" branch builds to
use JDK 21. I didn't yet touch the ones that run tests but will do
that after seeing if this round goes well. Ideally our test situation
would be in better shape :-/
On Wed, Jun 5, 2024 at 12:17 AM David Smiley wrote:
>
> We
We'll need to upgrade all the build servers (Apache, Thetaphi, Crave).
I started by choosing just the OWASP build for Solr as a trial to see
if it works without actually merging your PR.
On Tue, Jun 4, 2024 at 8:59 AM David Smiley wrote:
>
> +1 to move Solr main to Lucene's version (21) as soon
Let me know when you want me to update to JDK 21 on the Crave tests.
Thanks,
-Uv
On Tue, Jun 4, 2024 at 5:59 AM David Smiley wrote:
> +1 to move Solr main to Lucene's version (21) as soon as you wish.
> Like just go for it now if you are motivated. I echo Jan's preference
> to not make "sweepi
+1 to move Solr main to Lucene's version (21) as soon as you wish.
Like just go for it now if you are motivated. I echo Jan's preference
to not make "sweeping changes" yet however. On the server side, we
can be fairly up to date with Java versions. This does force plugin
writers (and people love
We are currently blocked from the latest OpenNLP because they moved to newer
Java.
You may be interested in https://github.com/apache/solr/pull/1510 and
https://github.com/apache/solr/pull/1999.
I’d love to see us starting to learn about what impacts Java 17 has. I suspect
once Lucene 10 s
Hi,
Thanks for starting the topic. Looks like we'll align Solr 10 with Lucene 10,
so somewhere between now and the release of Lucene 10 we definitely should make
the same move.
Our typical concern is if the change causes lots of other code changes that
makes backporting harder for a prolonged p
