[ https://issues.apache.org/jira/browse/LUCENE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409751#comment-13409751 ]
Robert Muir commented on LUCENE-3877: ------------------------------------- I think if we fix LUCENE-4202, we could just have a separate task for this that only runs on a fileset of non-test code? We could also exclude some tools like CheckIndex from it. We could add things like: System#in System#out System#err Throwable#printStackTrace() <-- eclipse stupid-stubs ... > 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 > Assignee: Michael McCandless > Fix For: 4.1 > > 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