[
https://issues.apache.org/jira/browse/SOLR-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524715#comment-17524715
]
David Smiley commented on SOLR-16158:
-------------------------------------
(assuming we want to do this at all) Yeah I tend to agree with Eric. It's a
balance... if we just move it to a module then it's just a dependency change
impact which is pretty easy for users to deal with, and no code change on their
part.
I wonder how realistic it is to not have solr-core depend on Jetty server jars.
I recall there are references in multiple places (e.g. for file upload
multi-part handling) that may not be easy to decouple. I guess we'll see :-)
The move away from the WAR was more than just literally not having a WAR; it
was a recognition that we are depending on Jetty; we don't want to deal with
the burden of being generic.
> Separate Solr Embedded from solr-core
> -------------------------------------
>
> Key: SOLR-16158
> URL: https://issues.apache.org/jira/browse/SOLR-16158
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Embedded
> Affects Versions: main (10.0)
> Reporter: Houston Putman
> Priority: Major
>
> Solr Embedded is a very useful way of running Solr within an application or
> test.
> However, it does not really need to be included in Solr Core. It should be in
> a separate module under {{/solr/embedded}}, so that Solr Core does not need
> to depend on Jetty Server jars.
> This can only really go into 10.0, since it will be a breaking change.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
