lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Bowyer (Updated) (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3877) Lucene should not call System.out.println
Date Wed, 21 Mar 2012 09:49:39 GMT


Greg Bowyer updated LUCENE-3877:


I took a guess that one way would be to replace the System IO streams with ones that will
throw exceptions.

It requires cglib, and might (due to the abuse of sun.reflect.Reflection to get the callee
efficiently) be sun hotspot specific.

I guess this is not perfect, it would only error out if the code is called

If there is thought to this being a good thing I could look into how to wire it up to the
> 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
>         Attachments:
> 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