[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229603#comment-14229603
]
Jan Høydahl commented on SOLR-4792:
-----------------------------------
Perhaps a solution is: Remove war from /dist but keep it in /server/webapps.
Then we don't commit to continue disting a war in 5.x, but downstream distros
and products currently bundling Solr with their app, will have a quick way of
using 5.x through an (unsupported) war, but at the same time get a sense of
urge that Solr will default to another network layer very soon.
Let's start to formulating the release text for 5.0, it will probably help
making decisions that will *benefit* users!
Question: Even if we bundle Solr with Netty or similar in the future, is should
not be a goal in itself to avoid people packaging Solr as a webapp to deploy in
Tomcat? Solr should be transport agnostic, and various contribs/plugins could
exist to support different ones.
> 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
