[
https://issues.apache.org/jira/browse/SOLR-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644452#comment-14644452
]
Timothy Potter commented on SOLR-7227:
--------------------------------------
yes, using latest patch you posted at 14:52 ...
We might as well address the extra folder now too ... the scripts affected are
minimal (smoketester, bin/solr, bin/solr.cmd, zkcli.sh/cmd, and a few in the
cloud-dev).
> 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]
