lucene-dev mailing list archives

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


Dawid Weiss commented on LUCENE-3877:

This is possible by verifying where System.out takes place at runtime via stack analysis.
Alternatively a bytecode woven aspect. But at the same time it could also be a find-and-grep
over sources? Comments would have to be removed in the pipeline prior to grepping for sysouts.

Checking all sysouts/syserrs and verifying stack traces there seems like an overkill compared
to the above.
> 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