Java autocomplete-plus provider for Atom editor. Current features:
Some planned future features:
Official page for package at atom.io: autocomplete-java
Configure classpath via a .classpath file. A simple project would typically contain a single .classpath file that is placed at the root directory of the project. A large project would contain a separate .classpath file for each module. An example of .classpath file contents:
There is an example of multimodule classpath setup on linter-javac Wiki.
You can alter the default .classpath filename and other autocomplete behavior with package settings.
At first, compile all your classes using your favorite build tool, and start your app. While editing java source files, lint and compile changed classes automatically with linter-javac, and the autocomplete-java package will refresh changed classes automatically on save. You can also reload changed classes automatically in JVM with spring-loaded or some other JVM agent. This way you can develop your app while the app is running.
NOTE: Current version of linter-javac performs bad in case of slow hard drive and large amount of classes to be linted. If you experience freezing during file save, consider disabling linter-javac, at least for now.
NOTE: Error in one class may prevent compilation of multiple classes. Therefore once you fix an error, multiple classes might be recompiled at once. So sometimes you might have to run 'project refresh' manually after you fix an error (ctrl-alt-shift-R). See issue #19.
Contributions are welcome. Please comment on issues you would like to contribute to, or add feature requests of your own.
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.