The extra nesting under /solr/ for a lot of things is quite annoying…. I’d be 
up for a new structure in Solr 11.


> On Jul 29, 2026, at 6:31 PM, David Smiley <[email protected]> wrote:
> 
> Our source repo has been only for Solr for some time now -- Lucene has
> left. Naturally, all of our sub-projects are underneath /solr because with
> Lucene around, doing anything else wouldn't have made any sense. But I
> don't think that makes sense anymore. I think moving some things to the
> top level would be useful to differentiate things... like what things do
> *not* go inside a running Solr server. For example cross-dc-manager and
> the Solr ref guide are rather different things that both don't run in a
> Solr server. They might ship with a Solr distribution but what we choose
> to bundle and not is rather arbitrary. The new UI module is a gray area
> but I'd vote outside. Packaging & distribution are both rather meta...
> maybe outside makes more sense.
> 
> Do others have thoughts on this?
> 
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley 
> <http://www.linkedin.com/in/davidwsmiley>

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast, a leader in email security and cyber 
resilience. Mimecast integrates email defenses with brand protection, security 
awareness training, web security, compliance and other essential capabilities. 
Mimecast helps protect large and small organizations from malicious activity, 
human error and technology failure; and to lead the movement toward building a 
more resilient world. To find out more, visit our website.

Reply via email to