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 <dsmi...@apache.org> 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 "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 their Solr plugins) so I don't think we > should pick 22 so as to not annoy our users who cannot upgrade > aggressively). > > We should not be so aggressive with SolrJ! Set the language there > (and thus solr-api, a dependency) to the 17 language / compiled-class > level, at least on the "main" (not test) codeline. The test codeline > uses solr-test-framework which uses solr-core thus that must always > match the server end. > > On Tue, Jun 4, 2024 at 1:47 AM sanjay dutt > <sanjaydutt.in...@yahoo.com.invalid> wrote: > > > > The purpose of this email thread is to initiate a discussion about > > upgrading the minimum Java version (Could be same as Lucene minimum Java > > for main branch i.e. 21) for the main branch. We seek to understand the > > community's major concerns and gather their guidance on this matter. > > Regards,Sanjay --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
