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

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

That patch does not work, cause some of Solr's dependencies require 
commons-lang on the classpath, e.g. {{org.apache.hadoop.fs.Path}}.

So even if we upgrade Solr as a whole to {{commons-lang3}}, we will still need 
to require {{commons-lang}} for the HDFS stuff. We could try to avoid having 
{{commons-lang}} in core, but then we'd have to factor out {{HdfsDirectory*}}, 
{{HdfsBackup*}}, {{HdfsTransactionLog}} mm from core into a separate HDFS 
contrib?

> 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