[
https://issues.apache.org/jira/browse/SOLR-17431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878666#comment-17878666
]
Eric Pugh commented on SOLR-17431:
----------------------------------
Two more places -p applies, the bin/solr start and bin/solr stop commands.
They don't show up in the java code since we craft the start/stop in the script
only...
> CLI: Resolve -p flag conflict (port, property, param, params)
> -------------------------------------------------------------
>
> Key: SOLR-17431
> URL: https://issues.apache.org/jira/browse/SOLR-17431
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: cli
> Affects Versions: 9.7, 9.6.1
> Reporter: Christos Malliaridis
> Priority: Major
> Labels: cli, newdev
>
> In the CLI analysis we found that -p is used for "port", "property", "param"
> and "params", in different CLI classes. Due to the potential confusion and
> mistakes new users may run into, we should remove the short variant for the
> less significant flags and keep the -p option only for the port flag (–port,
> currently used in RunExampleTool and SolrExporter).
> This is means that we have to deprecate for 9.8 the -p option for "property"
> in ConfigTool, for "param" in PackageTool and for "params" in PostTool, and
> remove the option completely in main / 10.0. *Do not* depricate the
> full-length flags though.
> When updating, make sure bin/solr, bin/solr.cmd and the documentation are all
> updated accordingly. The changes will be reflected afterwards in [Solr
> Arguments - Migration
> Overview|https://docs.google.com/spreadsheets/d/1ws44kN51WnGwQzOXc8KKRQ93TMgHSqIGb02MRWFel_U/edit?usp=sharing].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
