DonnieWest
commented
8 years ago I'm currently investigating where these issues are occuring. Any help would be greatly appreciated
Closed DonnieWest closed 8 years ago
DonnieWest
commented
8 years ago I'm currently investigating where these issues are occuring. Any help would be greatly appreciated
hsanson
commented
8 years ago I cannot replicate this issue. The auto completion works for me without issues in combination with the android plugin.
Also all classpath loading functions and custom gradle task are disabled if the javacomplete2 plugin is installed so I cannot see any reason for conflict.
I recommend you update the javacomplete2 plugin by completely removing it and re-installing it so the java parts of it get updated (re-compiled).
My configuration just in case:
NeoBundle 'artur-shaik/vim-javacomplete2'
let g:JavaComplete_Home = $HOME . '/.vim/bundle/vim-javacomplete2'
let $CLASSPATH .= '.:' . $HOME . '/.vim/bundle/vim-javacomplete2/libs/javavi/target/classes'
let g:JavaComplete_JvmLauncher = $HOME . '/Apps/jdk1.8.0_45/bin/java'
let g:JavaComplete_JavaCompiler = $HOME . '/Apps/jdk1.8.0_45/bin/javac'
let g:JavaComplete_GradleRepositoryDisabled = 1
let g:JavaComplete_MavenRepositoryDisabled = 0
let g:JavaComplete_GradlePath = "~/Apps/gradle/bin/gradle"I can replicate this using a minimal config of just your plugin and javacomplete2 with omnifunc set. Everything still works but classpath generation throws errors and fills my screen even though everything still works afterward
To replicate you might need to clear the cache javacomplete2 uses by rm -rf ~/.cache/javacomplete2 and then editing a file in an android gradle project
When Javacomplete2 and vim-android are used together, the following error is thrown when generating a $CLASSPATH for the first time