Java Linter

A Java linter for Visual Studio Code using the the language server protocol.

Features

javac-linter provides linting for Java sources using javac.

Tip: use ctrl-k ctrl-h to show javac-linterlogs

Requirements

JDK is required.

Settings

This extension contributes the following settings:

• javac-linter.enable: true or false (true by default)
• javac-linter.maxNumberOfProblems: max number of source code problems (20 by default)
• javac-linter.javac: Location of Java compiler executable (javac by default)
• javac-linter.classpath: project classpath array ([workspaceRoot] by default)

By example in settings.json:

{
  "javac-linter.enable": true,
  "javac-linter.maxNumberOfProblems": 100,
  "javac-linter.javac": "c:/Program Files/Java/jdk1.8.0_112/bin/javac.exe",
  "javac-linter.classpath": [
    "${workspaceRoot}/bin/classes"
  ]
}

Known Issues

Lint "on-fly" is not supported.

Take care when saving too quickly (ctrl-s the Java source), because each time when the document is saved, javac is executed.

Also .class files are generated inside of the first classpath.

Roadmap

• Allow full workspace linting (Maybe with performance issues)
• Allow suggested fix in case of a specific error/warning.

Release Notes

See CHANGELOG.md

Development

Note: JDK is required.

First, to compile server.js:

1. Open server directory in terminal.
2. Install dependencies: npm install
3. Compile and watch files: npm run compile

Second, to compile extension.js:

1. Open client directory in VSCode
2. Install dependencies: npm install
3. Use F5 to inspect and debug this extension

Note: Alternatively, you can copy this client folder to your .vscode/extension directory

Contributing

1. Fork it ( https://github.com/faustinoaq/vscde-javac-linter/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

Contributors

• @faustinoaq Faustino Aguilar - creator, maintainer