[ 
https://issues.apache.org/jira/browse/SOLR-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452216#comment-15452216
 ] 

Jan Høydahl commented on SOLR-9459:
-----------------------------------

I didn't say that it is deprecated. But we have earlier actively discouraged 
using the embedded mode for production if not absolutely necessary. See 
http://wiki.apache.org/solr/EmbeddedSolr

[~paranoiabla]'s use for development and testing is well within recommended use 
of Embedded, so not really an issue for him. However there should be really 
good reason for choosing Embedded for production - that would be a special 
case, and, as the wiki page says "less flexible, harder to support, not as well 
tested".

> Upgrade dependencies
> --------------------
>
>                 Key: SOLR-9459
>                 URL: https://issues.apache.org/jira/browse/SOLR-9459
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Petar Tahchiev
>         Attachments: commons-lang3.patch
>
>
> Hello,
> my project has more than 400 dependencies and I'm trying to ban the usage of 
> {{commons-collecrtions}} and {{commons-lang}} in favor of 
> {{org.apache.commons:commons-collection4}} and 
> {{org.apache.commons:commons-lang3}}. Unfortunately out of the 400 
> dependencies *only* solr is still using the old {{collections}} and {{lang}} 
> dependencies which are more than 6 years old.
> Is there a specific reason for that? Can you please update to the latest 
> versions:
> http://repo1.maven.org/maven2/org/apache/commons/commons-lang3/
> http://repo1.maven.org/maven2/org/apache/commons/commons-collections4/
> http://repo1.maven.org/maven2/org/apache/commons/commons-configuration2/
> http://repo1.maven.org/maven2/org/apache/commons/commons-io/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to