Russ Adams

If Vim is open twice and has a sw\* file for JavaImp.txt already, subsequent JavaImpInserts will fail.

JavaImpInsert is smart enough to call JavaImpGenerate when an import could not be found. However, the call to JIG ends the JavaImpInsert operation--regardless of whether an import could be found...

VimL can be challenging to work with, and Python may provide a better and more optimized solution. This is good timing because Neovim support Python again now.

It would be nice if the JavaDocs could be automatically generated based on the projects listed in g:JavaImpPaths. This would eliminate the need for the whole separate config variable g:JavaImpDocPaths.