[ https://issues.apache.org/jira/browse/LUCENE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235428#comment-13235428 ]
Dawid Weiss commented on LUCENE-3877: ------------------------------------- Oh, btw. I think a FindBugs rule for detecting sysouts/syserrs would be a great addition to FindBugs -- you should definitely file it as an improvement there. In reality at least class-level exclusions will be needed to avoid legitimate matches like the ones shown above (main methods, exception handlers), but these can be lived with. > Lucene should not call System.out.println > ----------------------------------------- > > Key: LUCENE-3877 > URL: https://issues.apache.org/jira/browse/LUCENE-3877 > Project: Lucene - Java > Issue Type: Bug > Reporter: Michael McCandless > Fix For: 3.6, 4.0 > > Attachments: IllegalSystemTest.java, IllegalSystemTest.java, > SystemPrintCheck.java > > > We seem to have accumulated a few random sops... > Eg, PairOutputs.java (oal.util.fst) and MultiDocValues.java, 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org