lucene-dev mailing list archives

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


Greg Bowyer commented on LUCENE-3877:

Well would it sway the argument if I said that the ASM code near directly translates into
a findbugs rule (I have done this before)

I was also not wanting to suggest findbug custom rules at the start because thats a bigger
change in including an entire code lint tool (unless its included with lucene already, in
which case forgive my stupidity I am still finding my way around)

Something doesn't fit right in my mind with the AspectJ approach, I have seen it not work
in the past for obscure reasons and it feels that running the weaving in pretend to check
the verbose output is not much further on from checking the source code in the first place.
> 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