4/12/2023 0 Comments Project eve studioSo, I was biased to think that error was related to Java version or stuff like that, but it was related to a lombok extension installed on VSCode. In my case I was having two exceptions: : javax/annotation/processing/AbstractProcessorĪnd : Then choose the command: Java: Open Java Language Server Log Fileīy doing this you can find the exactly exception that is happening. To do this press ctrl shift p to open the VSCode action prompt. Still I hope this helps all of you frustrated VSCode Java developers out there.įirst of all, check carefully the errors on VS Code log and try to not get biased by the community common errors. Obviously these are bugs in the plugins which I will report to the GitHub contributors, but for now we will have to live with a little manual work. Maven handles this fine, but apparently the VSCode Java builder does not. In my case it was a conflict as I had two AppConfig.java files, one in main and one in test. This will open a log file which is normally not displayed when building your Java code, and will tell you exactly what went wrong with the build. Then choose the command: Java: Open Java Language Server Log File Next press ctrl shift p (in my case) to open the VSCode action prompt. If you can't find it at this location, simply search for the folder workspaceStorage. This folder was in my case located in (Windows 10): C:\Users\\AppData\Roaming\Code\User\workspaceStorage This was fixed by clearing the VSCode workspaceStorage folder completely! The name of my application (artifact) did not match the name in the Java Dependencies tree view. So this didn't work for me, but I found out what did.įirst of all looking at the Java Dependencies plugin gave me a hint that something was out of sync. We are not very far into the project and I am already receiving pressure to switch to. The Spring Framework seems ideal for our purposes but the tooling, not so much. The project we are working on is intended for open source distribution. I have to say that we are spending way too much time resolving issues with tools and dependencies and not enough time on the app. I suspect the RedHat VSCode plugin for Java is in the mix but need help figuring out how to work around the issue. There is something going on in VSCode that's not being reported anywhere that I can find. The project builds, and packages in Maven just fine and it can be debugged in attach mode which is tedious at best. However there are no errors reported in the PROBLEMS, OUTPUT, DEBUG CONSOLE or TERMINAL tabs. Obviously the "Debugger for Java" extension thinks there is a build problem. I have a project that builds perfectly in Maven and when I launch the debugger in Visual Studio Code this notification appears in the lower right-hand corner of the VSCode window. Not sure but if anyone from the RedHat project reads this, it looks to me like a bug, or deficiency. Wiping out the workspace cache caused the plugin to recreate project data from the maven spec. classpath file was out of sync with the POM file. Apparently the RedHat-Developer plugin managed to get out of sync. I had renamed a number of folders, class names and packages. Here is a link to the relvant page: VSCODE Clean Workspace Directory. Problem solved I resolved this issue by clearing the workspace cache in VS code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |