[
https://issues.apache.org/jira/browse/SOLR-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003291#comment-17003291
]
Erick Erickson commented on SOLR-14149:
---------------------------------------
bq. The layout of the distribution is documented in solr/README.txt
Right, and it says:
server/
A self-contained Solr instance, complete with a sample
configuration and documents to index. Please see: bin/solr start -help
for more information about starting a Solr server.
And under that we have
./solr-webapp/webapp/WEB-INF/lib/
./lib
and at least copies of these in each.
jetty-http-9.4.19.v20190610.jar
jetty-util-9.4.19.v20190610.jar
jetty-io-9.4.19.v20190610.jar
We have no guidance there about _why_ someone would care about what's in which
directory. Fortunately it "just works".
Here's the comment about the dist directory:
dist/solr-<component>-XX.jar
The Apache Solr libraries. To compile Apache Solr Plugins,
one or more of these will be required. The core library is
required at a minimum. (see http://wiki.apache.org/solr/SolrPlugins
for more information).
But no mention of dist/solrj-lib, which is necessary for anyone compiling, say,
an external indexing program (which we recommend in other places).
Anyway, I doubt it's worth much more debate, probably well to revisit this
sometime after the Gradle build becomes a reality.
> Remove non-changes from CHANGES.txt
> -----------------------------------
>
> Key: SOLR-14149
> URL: https://issues.apache.org/jira/browse/SOLR-14149
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
>
> Our CHANGES.txt should just list our changes / release notes. Nothing else.
> * no Introduction
> * no "Getting Started"
> * no "Versions of Major Components" with each release.
> We have a website, a reference guide, and a README.md that are all more
> suitable places. Lets not maintain it here as well; lets keep this file
> focused on it's namesake. We can/should *link* to that information from
> CHANGES.txt. For example linking to
> https://lucene.apache.org/solr/guide/8_4/solr-upgrade-notes.html is highly
> appropriate as it's a more user friendly editorialized version of CHANGES.txt.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
