Davide, NbErrorManager is another candidate for "refactoring" (total
rewrite, I am serious).  In the beginning of the file there is

    /** Minimum value of severity to write message to the log file*/
    private int minLogSeverity = ErrorManager.INFORMATIONAL; // NOI18N

but later in the same file

    public boolean isLoggable (int severity) {
        // logging severity is more important - by default INFORMATIONAL
        // messages are not logged
        severity = severity >> 1;
        return severity >= minLogSeverity;
    }

I am sorry but I don't think that changing the behaviour now is a good
idea. there might be modules that use this severity already and we
could cause a huge amount of log messages from those modules.

Workaround: use different severity for logging.

Note: please note that there may be other impls of ErrorManager so
putting informational can make sense for someone who don't want our
NbErrorManager to do anything but his/her ErrorManager to e.g.
selectively log messages with this severity.

Resolved for 3.4.x or earlier, no new info since then -> verified.

Resolved for 3.4.x or earlier, no new info since then -> closing.