[
https://issues.apache.org/jira/browse/SOLR-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644493#comment-14644493
]
Shawn Heisey commented on SOLR-7227:
------------------------------------
bq. Otherwise do you have an opinion about the extra inner folder
solr-webapp/webapp?
I'm not sure we should move the artifacts out of the inner webapp directory, at
least not until the next major version.
My concern is not our own scripts. We can change those easily enough. The
potential problem is homegrown scripts written by users. If we move the
extracted artifacts, even just one directory level, we risk problems with
highly customized user setups.
Is it enough to assume someone who builds their own scripts will be able to use
a note in the "upgrading from" section of CHANGES.txt to figure out how to fix
their setup when they upgrade? It might be. User confusion is always a worry
for me, because Solr already has plenty to offer in that department.
I can't imagine based on anything you've said that I would want to vote -1. I
offer my thoughts only for consideration.
Semi-related: I need to find out what we've got for documentation on upgrading
a Solr 5.x install to the next release. I have some ideas about how I would do
it, but I'd like to know what (if anything) we are saying officially.
> Solr distribution archive should have the WAR file extracted already
> --------------------------------------------------------------------
>
> Key: SOLR-7227
> URL: https://issues.apache.org/jira/browse/SOLR-7227
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.0
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Fix For: 5.3, Trunk
>
> Attachments: SOLR-7227-part2.patch, SOLR-7227-part2.patch,
> SOLR-7227-part2.patch, SOLR-7227-part2.patch, SOLR-7227-part2.patch,
> SOLR-7227.patch, SOLR-7227.patch
>
>
> Currently, there is still the solr.war file in the server/webapps directory,
> which gets extracted upon first startup of Solr. It would be better to ship
> Solr with the WAR already extracted, thus taking us one step closer to truly
> not shipping a WAR file. Moreover, some users have reported not being able to
> make /opt/solr truly read-only because of the need to extract the WAR
> on-the-fly upon first startup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
