[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229966#comment-14229966
]
Steve Molloy commented on SOLR-4792:
------------------------------------
I think all that is missing on this ticket is a link to the stuff that removing
the WAR is expected to fix. I mean I think I agree with the approach, but only
because I can kind ofo guess at what issues we're trying to solve by reading
different discussions and such. There has been talks about deadlocks,
connections, and all sorts of optimizations that are currently not possible
because of the fact that Solr is a webapp shipped as a WAR that must work on
any webapp container. So, where are the entries for these optimizations that
need to be made? If you have half a dozen of those that are all depending on
not being a war that can run on any container, then people will stop asking why
we're removing a war and we can get back to actually implementing improvements.
:)
> stop shipping a war in 5.0
> --------------------------
>
> Key: SOLR-4792
> URL: https://issues.apache.org/jira/browse/SOLR-4792
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Mark Miller
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-4792.patch
>
>
> see the vote on the developer list.
> This is the first step: if we stop shipping a war then we are free to do
> anything we want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
