[
https://issues.apache.org/jira/browse/SOLR-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644514#comment-14644514
]
Shawn Heisey commented on SOLR-7227:
------------------------------------
bq. But custom scripts may already break because there is no WAR anymore.
Very true, and that is something that I had not considered. I also have no
strong opinion, and it sounds like this entire change is destined to lead to
user confusion, so let's jump in all the way!
> 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]
