SOLR-17161 is merged to main, branch_10x and branch_10_0, and CHANGELOG.md re-generated on branch_10_0. Thanks for the patience. I kicked the tires of https://ci-builds.apache.org/job/Solr/job/Solr-Smoketest-10.0/ to get a new run...
Jan > 11. jan. 2026 kl. 19:01 skrev Anshum Gupta <[email protected]>: > > Thanks a lot, Jan and David. > > The SOLR-17161 PR looks good and ready to be merged pretty much, so let’s > get it in considering that it needs to happen in a major version. Do you > know when you’d be confident to merge the PR into 10.0? > > I can build an RC right after you merge, and folks can continue testing the > old RC for everything else anyways if they want to. > > Anshum Gupta > > > On Sat, Jan 10, 2026 at 5:03 PM Jan Høydahl <[email protected]> wrote: > >> PR #4039 is merged, and I created >> https://issues.apache.org/jira/browse/SOLR-18069 to remember to add some >> smoke testing of maven files. I'll try to run the same maven test on RC2... >> >> WRT solrj-jetty module, there have been some more review and improvements, >> thanks. I sense some enthusiasm for it, but whether it shuold hold the >> release is ultimately not up to me.. >> >> Jan >> >>> 8. jan. 2026 kl. 12:17 skrev Jan Høydahl <[email protected]>: >>> >>> Prepared a potential fix for the maven thing: >> https://github.com/apache/solr/pull/4039 - there may be other ways to fix >> it too >>> >>> Also, I tok a stab at https://issues.apache.org/jira/browse/SOLR-17161 >> yesterday and wonder what you guys think about a bit of late feature creep >> for the 10.0 release 🙈 >>> It will split jetty-client out of (core) solrj maven package, meaning >> that solrj users who only need *JdkSolrClient can get away with less >> required solrj dependencies. >>> It was intended for 10.0 but pushed to 10.1 this autumn, when the 10.0 >> release was originally planned. >>> >>> David has reviewed the PR and can speak for the risk. >>> If we don't do this now, the next "train" is 11.0, which would give >> another solrj back-break for users. >>> >>> Jan >>> >>>> 7. jan. 2026 kl. 22:40 skrev Anshum Gupta <[email protected]>: >>>> >>>> Thanks for the testing, Jan! >>>> >>>> This vote is now 'failed'. I'll spin out a new RC once we have the fixes >>>> and we can vote on it again. If folks are interested, the binaries >> should >>>> be good to be tested until the next RC is out as they'll stay the same. >>>> >>>> On Wed, Jan 7, 2026 at 7:41 AM Jan Høydahl <[email protected]> >> wrote: >>>> >>>>> I think I found a serious flaw in the maven artifacts. See solr-api's >> POM >>>>> file at >>>>> >> https://dist.apache.org/repos/dist/dev/solr/solr-10.0.0-RC1-rev-472cdaf4bb28e0b3237e310339c880b720221432/solr/10.0.0/maven/org/apache/solr/solr-api/10.0.0/solr-api-10.0.0.pom >>>>> >>>>> It tries to pull in our platform module as pom: >>>>> >>>>> <dependencyManagement> >>>>> <dependencies> >>>>> <dependency> >>>>> <groupId>org.apache</groupId> >>>>> <artifactId>platform</artifactId> >>>>> <version>10.0.0</version> >>>>> <type>pom</type> >>>>> <scope>import</scope> >>>>> </dependency> >>>>> >>>>> Note how it pulls org.apache:platform as maven coordinates. Which of >>>>> course do not exist... >>>>> >>>>> I found it by first running gradlew mavenToLocalRepo (here on main >> branch, >>>>> but same on 10_0) to install snapshot locally, then make a small solrj >> test >>>>> project which imports the snapshot: >>>>> >>>>> mvn dependency:tree >>>>> [INFO] Scanning for projects... >>>>> [INFO] >>>>> [INFO] -----------------------< org.example:testsolrj >>>>>> ------------------------ >>>>> [INFO] Building testsolrj 1.0-SNAPSHOT >>>>> [INFO] from pom.xml >>>>> [INFO] --------------------------------[ jar >>>>> ]--------------------------------- >>>>> [INFO] >>>>> >> ------------------------------------------------------------------------ >>>>> [INFO] BUILD FAILURE >>>>> [INFO] >>>>> >> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 0.107 s >>>>> [INFO] Finished at: 2026-01-07T16:31:26+01:00 >>>>> [INFO] >>>>> >> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal on project testsolrj: Could not collect >>>>> dependencies for project org.example:testsolrj:jar:1.0-SNAPSHOT >>>>> [ERROR] Failed to read artifact descriptor for >>>>> org.apache.solr:solr-api:jar:11.0.0-SNAPSHOT >>>>> [ERROR] Caused by: The following artifacts could not be >> resolved: >>>>> org.apache:platform:pom:11.0.0-SNAPSHOT (absent): Could not find >> artifact >>>>> org.apache:platform:pom:11.0.0-SNAPSHOT >>>>> >>>>> I'll have to give this RC a -1 >>>>> >>>>> Our smoke tester should probably try to use the maven/ folder as a >> local >>>>> mvn repo to build and compile an app using solrj... >>>>> >>>>> Jan >>>>> >>>>> >>>>>> 7. jan. 2026 kl. 12:46 skrev Jan Høydahl <[email protected]>: >>>>>> >>>>>> SUCCESS! [0:45:12.437198] >>>>>> >>>>>> I see that the generated CHANGELOG.md has some issues >>>>>> * The [10.0.0] section should not have a release date (as we still >> don't >>>>> know what date it will be). I thought the wizard would delete >>>>> changelog/v10.0.0/releast-date.txt automatically before committting... >>>>>> * The [9.10.0] section SHOULD have had a release date (i.e. a >>>>> changelog/v9.10.0/release-date.txt), probably needs to be added as a >> commit >>>>> at the end of a release. >>>>>> >>>>>> I checked the maven/ folder a bit more, and good news, solr-solrj does >>>>> not depend on zookeeper libs anymore, nor apache-httpclient. >>>>>> SolrJ still requires a lot of jetty libs (even if you use >> JdkSolrClient, >>>>> but that is expected. Here is the dependency graph of solrj. Is there >>>>> anything more here we could have got rid of or shaded? >>>>>> >>>>>> org.apache.solr:solr-solrj:10.0.0 >>>>>> ├── org.apache.solr:solr-api:10.0.0 (compile) >>>>>> │ ├── com.fasterxml.jackson.core:jackson-annotations:2.20.0 >> (compile) >>>>>> │ ├── io.swagger.core.v3:swagger-annotations-jakarta:2.2.22 >> (compile) >>>>>> │ ├── jakarta.ws.rs:jakarta.ws.rs-api:3.1.0 (runtime) >>>>>> │ ├── org.semver4j:semver4j:6.0.0 (runtime) >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 (runtime) >>>>>> │ >>>>>> ├── org.eclipse.jetty.http2:jetty-http2-client:12.0.27 (compile) >>>>>> │ ├── org.eclipse.jetty:jetty-alpn-client:12.0.27 >>>>>> │ │ ├── org.eclipse.jetty:jetty-io:12.0.27 >>>>>> │ │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ ├── org.eclipse.jetty.http2:jetty-http2-common:12.0.27 >>>>>> │ │ ├── org.eclipse.jetty.http2:jetty-http2-hpack:12.0.27 >>>>>> │ │ │ ├── org.eclipse.jetty:jetty-http:12.0.27 >>>>>> │ │ │ ├── org.eclipse.jetty:jetty-io:12.0.27 >>>>>> │ │ │ ├── org.eclipse.jetty:jetty-util:12.0.27 >>>>>> │ │ │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── com.fasterxml.jackson.core:jackson-databind:2.20.0 (runtime) >>>>>> │ ├── com.fasterxml.jackson.core:jackson-annotations:2.20.0 >>>>>> │ └── com.fasterxml.jackson.core:jackson-core:2.20.0 >>>>>> │ >>>>>> ├── com.fasterxml.jackson.core:jackson-annotations:2.20.0 (runtime) >>>>>> │ >>>>>> ├── com.fasterxml.jackson.core:jackson-core:2.20.0 (runtime) >>>>>> │ >>>>>> ├── org.slf4j:slf4j-api:2.0.17 (runtime) >>>>>> │ >>>>>> ├── org.eclipse.jetty.http2:jetty-http2-client-transport:12.0.27 >>>>> (runtime) >>>>>> │ ├── org.eclipse.jetty:jetty-alpn-java-client:12.0.27 >>>>>> │ ├── org.eclipse.jetty:jetty-client:12.0.27 >>>>>> │ ├── org.eclipse.jetty.http2:jetty-http2-client:12.0.27 >> (duplicate) >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── org.eclipse.jetty:jetty-http:12.0.27 (runtime) >>>>>> │ ├── org.eclipse.jetty:jetty-io:12.0.27 >>>>>> │ ├── org.eclipse.jetty:jetty-util:12.0.27 >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── org.eclipse.jetty:jetty-client:12.0.27 (runtime) >>>>>> │ ├── org.eclipse.jetty:jetty-alpn-client:12.0.27 >>>>>> │ ├── org.eclipse.jetty:jetty-http:12.0.27 >>>>>> │ ├── org.eclipse.jetty:jetty-io:12.0.27 >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── org.eclipse.jetty:jetty-util:12.0.27 (runtime) >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── org.eclipse.jetty:jetty-io:12.0.27 (runtime) >>>>>> │ ├── org.eclipse.jetty:jetty-util:12.0.27 >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> ├── org.slf4j:jcl-over-slf4j:2.0.17 (runtime) >>>>>> │ └── org.slf4j:slf4j-api:2.0.17 >>>>>> │ >>>>>> └── org.eclipse.jetty:jetty-alpn-java-client:12.0.27 (runtime) >>>>>> ├── org.eclipse.jetty:jetty-alpn-client:12.0.27 >>>>>> └── org.slf4j:slf4j-api:2.0.17 >>>>>> >>>>>> I'm not casting a vote at this time... >>>>>> >>>>>> Jan >>>>>> >>>>>>> 7. jan. 2026 kl. 01:51 skrev Anshum Gupta <[email protected]>: >>>>>>> >>>>>>> After much waiting, please vote for Release Candidate 1 for Solr >> 10.0.0 >>>>>>> >>>>>>> *The artifacts can be downloaded from*: >>>>>>> >>>>> >> https://dist.apache.org/repos/dist/dev/solr/solr-10.0.0-RC1-rev-472cdaf4bb28e0b3237e310339c880b720221432 >>>>>>> >>>>>>> *You can run the smoke tester directly with this command*: >>>>>>> >>>>>>> python3 -u dev-tools/scripts/smokeTestRelease.py \ >>>>>>> >>>>> >> https://dist.apache.org/repos/dist/dev/solr/solr-10.0.0-RC1-rev-472cdaf4bb28e0b3237e310339c880b720221432 >>>>>>> >>>>>>> You can build a release-candidate of the official docker images >> (full & >>>>>>> slim) using the following command: >>>>>>> >>>>>>> SOLR_DOWNLOAD_SERVER= >>>>>>> >>>>> >> https://dist.apache.org/repos/dist/dev/solr/solr-10.0.0-RC1-rev-472cdaf4bb28e0b3237e310339c880b720221432/solr >>>>>>> && \ >>>>>>> docker build >>>>> $SOLR_DOWNLOAD_SERVER/10.0.0/docker/Dockerfile.official-full >>>>>>> \ >>>>>>> --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ >>>>>>> -t solr-rc:10.0.0-1 && \ >>>>>>> docker build >>>>> $SOLR_DOWNLOAD_SERVER/10.0.0/docker/Dockerfile.official-slim >>>>>>> \ >>>>>>> --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ >>>>>>> -t solr-rc:10.0.0-1-slim >>>>>>> >>>>>>> The vote will be open for at least for 10 days, until 2026-01-16 >> 01:00 >>>>> UTC >>>>>>> or until it's considered failed. >>>>>>> >>>>>>> [ ] +1 approve >>>>>>> [ ] +0 no opinion >>>>>>> [ ] -1 disapprove (and reason why) >>>>>>> >>>>>>> Here is my +1 >>>>>>> >>>>>>> SUCCESS! [0:51:16.744464] >>>>>>> >>>>>>> -Anshum Gupta >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> Anshum Gupta >>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
