Hi Jan, The pointers are at my local fork but I filed a patch that updates the Java version for Lucene 10, here: https://github.com/apache/lucene/pull/11872
Dawid On Tue, Oct 25, 2022 at 12:07 PM Jan Høydahl <jan....@cominvent.com> wrote: > > That's a good question. The wizard already has a mapping from Solr version to > Java version and a method to find correct java_home and java_cmd: > https://github.com/dweiss/lucene/blob/main/dev-tools/scripts/releaseWizard.py#L590:L600 > > So perhaps we need some logic to set correct JAVA_HOME and path for each > command depending on branch? > > Also the Java version for Lucene 10 (main) must be updated here > https://github.com/dweiss/lucene/blob/main/dev-tools/scripts/releaseWizard.py#L69:L70 > > Jan > > 25. okt. 2022 kl. 10:49 skrev Dawid Weiss <dawid.we...@gmail.com>: > > >> I think the problem here is that at the point of running those commands I >> had lost trust in the release wizard and I was running the commands manually. > > > Ok, that explains it. :) > >> >> One of the problems at the moment in the release wizard is that any step >> that involves running a gradle task on main branch fails because it requires >> java 17 and we run all commands with java 11. I think that should be >> addressed, those steps were missing for the 9.4.0 release and I fixed them >> too. > > > I'm not sure how to handle cross-major version releases with the release > wizard. Should the wizard/scripts from 9x be used (and not the main version)? > > Dawid > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
