[
https://issues.apache.org/jira/browse/SOLR-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878218#comment-17878218
]
ASF subversion and git services commented on SOLR-17429:
--------------------------------------------------------
Commit 26d00c38b23e53f4859c0fc454e496706f568504 in solr's branch
refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=26d00c38b23 ]
SOLR-17429, SOLR-17338: Use stderr for SolrCLI deprecation logs (#2679)
> Find more permanent solution to Deprecated SolrCLI logging
> ----------------------------------------------------------
>
> Key: SOLR-17429
> URL: https://issues.apache.org/jira/browse/SOLR-17429
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: cli
> Affects Versions: 9.7
> Reporter: Houston Putman
> Assignee: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Commons CLI now supports deprecated options, and when those options are used,
> they print a log to the user warning them. Unfortunately, by default, the
> logging is done to stdout. Tools that use the SolrCLI and parse the output
> will be broken by this change since they generally always read from stdout.
> If the logging was done to stderr, there would be no problem since the tools
> would not read the deprecation logs with the CLI output.
> Either
> * Commons CLI should log deprecations to stderr by default
> * Commons CLI should make {{Option.toDeprecatedString()}} public, so that we
> can more easily make our own DeprecationHandler that merely prints the same
> thing to stderr. As it is, we have to copy the whole method ourselves since
> it is package private.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
