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

Christine Poerschke commented on SOLR-14067:
--------------------------------------------

Hello. I did some digging into test failures too this evening and noticed these 
two {{lib}} variants, maybe intended, maybe not, just jumped out as surprising 
to me.

{code}
$ git grep -h ".lib.*solr\-scripting.*jar"
  <lib dir="${solr.install.dir:../../../../../}/contrib/scripting/build/libs/" 
regex="solr-scripting-\d.*\.jar" />
  <lib dir="${solr.install.dir:../../../..}/dist/" 
regex="solr-scripting-\d.*\.jar" />
{code}

> Move StatelessScriptUpdateProcessor to a contrib
> ------------------------------------------------
>
>                 Key: SOLR-14067
>                 URL: https://issues.apache.org/jira/browse/SOLR-14067
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ishan Chattopadhyaya
>            Assignee: David Eric Pugh
>            Priority: Major
>             Fix For: master (9.0)
>
>          Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> Move server-side scripting out of core and into a new contrib.  This is 
> better for security.
> Former description:
> ----
> We should eliminate all scripting capabilities within Solr. Let us start with 
> the StatelessScriptUpdateProcessor deprecation/removal.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to