Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-3877

Lucene should not call System.out.println

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      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)...?

        Attachments

        1. IllegalSystemTest.java
          2 kB
          Greg Bowyer
        2. IllegalSystemTest.java
          2 kB
          Greg Bowyer
        3. SystemPrintCheck.java
          5 kB
          Greg Bowyer
        4. LUCENE-3877.patch
          2 kB
          Robert Muir
        5. LUCENE-3877.patch
          51 kB
          Robert Muir

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: