[ https://issues.apache.org/jira/browse/LUCENE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231095#comment-13231095 ]
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: https://issues.apache.org/jira/browse/LUCENE-3877 > 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, 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