[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207595#comment-14207595
]
Jayson Minard commented on SOLR-4792:
-------------------------------------
I agree with the comments from the mailing list, and they are not mutually
exclusive with a WAR. I'm not sure we need a WAR, but you can always adapt
to one (as an example, ElasticSearch for example has
elasticsearch-transport-wares to do this)
App servers don't prevent better ways of doing configuration, and usually
everything needs at least a starting point to find a configuration whether
it is a war or a command-line tool. It can be available for both.
Not that I'm all pro WAR anyway since I obviously moved away from it
myself, but there are already solutions that make it easier while it is
still a WAR. That is just a bundling of everything needed to run...
Either way, it should be easier to configure and use.
On Wed, Nov 12, 2014 at 12:14 AM, Shawn Heisey (JIRA) <[email protected]>
> stop shipping a war in trunk (6.0)
> ----------------------------------
>
> Key: SOLR-4792
> URL: https://issues.apache.org/jira/browse/SOLR-4792
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 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: [email protected]
For additional commands, e-mail: [email protected]
