[
https://issues.apache.org/jira/browse/SOLR-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644506#comment-14644506
]
Uwe Schindler commented on SOLR-7227:
-------------------------------------
Smoke tester passes for me on Linux. There is an unrelated bug in smoker when
it tries to execute post.jar (it does not setup PATH correctly as its does for
the scripts), so it fails if you have no "java" in your path, or it executes
the wrong Java (maybe older version). I will open separate issue, its really
unrelated. It just costed me half an hour :(
Shawn: I have no strong opinion, we can leave it as it is. But custom scripts
may already break because there is no WAR anymore. In previous versions, Jetty
extracted the WAR to a temporary folder, so the scripts will for sure no longer
work.
> 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]
