Lucene - Core
  1. Lucene - Core
  2. LUCENE-3877

Lucene should not call System.out.println

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA, 5.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)...?

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

        Activity

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development