lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luca Cavanna (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3877) Lucene should not call System.out.println
Date Fri, 16 Mar 2012 15:19:39 GMT


Luca Cavanna commented on LUCENE-3877:

I feel guilty...maybe because I wrote that code :) yeah, that one should be System.err.
I thought at least the command line tool usage could be System.out, but that's already System.err
for example in IndexUpgrader, so... looks like everything should be System.err. But that's
the behaviour for command line tools. "Normal" classes shouldn't have System.err either I
guess. Maybe we should mark command line tools as special classes in some way in order to
give them more freedom?

> Lucene should not call System.out.println
> -----------------------------------------
>                 Key: LUCENE-3877
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Michael McCandless
>             Fix For: 3.6, 4.0
> We seem to have accumulated a few random sops...
> Eg, (oal.util.fst) and, at least.
> Can we somehow detect (eg, have a test failure) if we accidentally leave errant System.out.println's
(leftover from debugging)...?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message