[
https://issues.apache.org/jira/browse/SOLR-17790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986920#comment-17986920
]
ASF subversion and git services commented on SOLR-17790:
--------------------------------------------------------
Commit 8a3e4c87a3b167fe276efaac2621d5ce5646122e in solr's branch
refs/heads/fix-native-access-warning from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=8a3e4c87a3b ]
SOLR-17790: Allow -j option to start with a dash (#3392)
> Fix Solr start with Jetty options "-j" that start with a dash
> -------------------------------------------------------------
>
> Key: SOLR-17790
> URL: https://issues.apache.org/jira/browse/SOLR-17790
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 9.8
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Blocker
> Fix For: 9.9
>
>
> SOLR-6962 improved the checking of command line options sent to Solr, however
> the checks were to strict on the {{–j}} or {{–jettyconfig}} option. It didn't
> allow for starting the value with a dash ({{–}}). Since most jetty config
> options will start with a dash, such as "––module=...", this is problematic.
> The fix is to remove this condition in the check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
