JDK-8150856 : Inconsistent API documentation for @param caller in System.LoggerFinder.getLogger
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-02-29
  • Updated: 2016-06-13
  • Resolved: 2016-03-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b109Fixed
Related Reports
Relates :  
Description
The javadoc says:

        /**
         * Returns an instance of {@link Logger Logger}
         * for the given {@code caller}.
         *
         * @param name the name of the logger.
         * @param caller the class for which the logger is being requested;
         *               can be {@code null}.
         *
         * @return a {@link Logger logger} suitable for the given caller's
         *         use.
         * @throws NullPointerException if {@code name} is {@code null} or
         *        {@code caller} is {@code null}.
         * @throws SecurityException if a security manager is present and its
         *         {@code checkPermission} method doesn't allow the
         *         {@code RuntimePermission("loggerFinder")}.
         */
        public abstract Logger getLogger(String name, /* Module */ Class<?> caller);

@throws NullPointerException  is correct; 'can be null' must be removed from @param caller.