NPE in javadoc

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P2
    • 8
    • Affects Version/s: None
    • Component/s: tools
    • b100
    • Verified

      (From Brian Goetz via direct email)

      Running from lambda tip:

      java.lang.NullPointerException
              at com.sun.tools.doclint.Messages$Options.isEnabled(Messages.java:192)
              at com.sun.tools.doclint.Messages.report(Messages.java:116)
              at com.sun.tools.doclint.Messages.error(Messages.java:96)
              at com.sun.tools.doclint.Checker.visitErroneous(Checker.java:767)
              at com.sun.tools.doclint.Checker.visitErroneous(Checker.java:88)
              at com.sun.tools.javac.tree.DCTree$DCErroneous.accept(DCTree.java:333)
              at com.sun.source.util.DocTreePathScanner.scan(DocTreePathScanner.java:65)
              at com.sun.source.util.DocTreeScanner.scan(DocTreeScanner.java:92)
              at com.sun.source.util.DocTreeScanner.scanAndReduce(DocTreeScanner.java:100)
              at com.sun.source.util.DocTreeScanner.visitDocComment(DocTreeScanner.java:141)
              at com.sun.tools.doclint.Checker.visitDocComment(Checker.java:189)
              at com.sun.tools.doclint.Checker.visitDocComment(Checker.java:88)
              at com.sun.tools.javac.tree.DCTree$DCDocComment.accept(DCTree.java:122)
              at com.sun.source.util.DocTreePathScanner.scan(DocTreePathScanner.java:47)
              at com.sun.tools.doclint.Checker.scan(Checker.java:155)
              at com.sun.tools.doclint.DocLint.scan(DocLint.java:336)
              at com.sun.tools.javadoc.DocImpl.comment(DocImpl.java:133)
              at com.sun.tools.javadoc.DocImpl.tags(DocImpl.java:165)
              at com.sun.tools.doclets.formats.html.PackageWriterImpl.addDeprecationInfo(PackageWriterImpl.java:139)
              at com.sun.tools.doclets.formats.html.PackageWriterImpl.getPackageHeader(PackageWriterImpl.java:108)


      This is caused by @@@ appearing in the text of package-info.java. Obviously that's some bad javadoc'ing (but also shouldn't crash the tool.) From the stack trace, I think what's happening is that the bug is in the reporting of the diagnostic?

            Assignee:
            Jonathan Gibbons
            Reporter:
            Jonathan Gibbons
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: