Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

verboseLogging

Florian Breisch edited this page Mar 2, 2016 · 2 revisions

Type: boolean
Default: false

Description

Enabling verboseLogging lets linter-javac log useful information around the whole liniting-process. This is primarily meant to be used if the linter is not working as expected.

In that case you might temporarily enable verboseLogging, open the developer-tools (cmd+alt+i) then save some faulty Java-files and watch the output in the developer-console.

At this point of the linters evolution linter-javac is not able to detect itself, if everything is working fine (we're planning to change that with the upcoming 2.0.0-release). At the end of every lint-process the complete stderr-output of the javac-invocation is logged into the console. If something went wrong you probably should see any error-messages there.

However, the logging-mechanism is intended to be proof-read by the package-maintainers. To get help with your linter-javac-instance, feel free to open an issue and post the log-data. We would really appreciate if you help us improving linter-javac.