adityamparikh opened a new pull request, #167:
URL: https://github.com/apache/solr-mcp/pull/167

   ## Motivation
   
   The Solr 10 compatibility docs still say:
   
   > **SolrJ 10.x dependency:** Not yet on Maven Central (as of 2026-03-06); 
tests use SolrJ 9.x against a Solr 10 server. Update `solr-solrj` and Jetty BOM 
when 10.x is released.
   
   Every part of that is now false:
   
   - **SolrJ 10.x is on Maven Central.** 
`https://repo1.maven.org/maven2/org/apache/solr/solr-solrj/10.0.0/solr-solrj-10.0.0.pom`
 returns 200, and `mavenCentral()` is the build's only declared repository.
   - **`solr-solrj` is already updated.** #58 bumped it 9.9.0 → 10.0.0 on 
2026-03-24, 18 days after the note was written; `gradle/libs.versions.toml` has 
pinned `solr = "10.0.0"` since.
   - **The version skew is the reverse of what's written.** `solr.test.image` 
defaults to `solr:9.9-slim`, so the standard build exercises a SolrJ 10 
*client* against a Solr 9.9 *server*, not a SolrJ 9 client against Solr 10.
   - **The Jetty BOM action item is moot.** The Jetty artifacts are declared 
versionless and managed by Spring Boot's BOM — there is no separate pin to 
update.
   
   This matters because it reads as an open action item ("update `solr-solrj` 
... when 10.x is released") for work that was completed four months ago, and it 
misdescribes what the test suite actually covers.
   
   ## Changes
   
   Restates the bullet as current fact, and notes the 
client-newer-than-default-server skew since that's the genuinely useful thing 
for a contributor to know.
   
   Corrected in both places the claim appears:
   - `AGENTS.md` (which `CLAUDE.md` symlinks to)
   - `dev-docs/DEVELOPMENT.md`
   
   Docs only — no code or build changes.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to