You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is too early to test and measure with javac implementation. But anyway I just wanted to see how it goes.
I was trying to load the https://github.com/Azure/azure-sdk-for-java in VSCode for debugging an issue. When I try to load this project with JDT it takes around ~ 10min or less with project 2K errors. When I try to load the same with Javac it takes around more than 15min with 10k project errors.
I think project errors are due to something I'm missing to do prior to importing. But the time it takes to run the import has a huge difference and also the responsiveness of VSCode.
Also in JDT mode regardless I had 2K errors, I could run some of unit tests and work with the code base. But in Javac mode the same tests cannot be executed since the java-debug fails to find the compiled classes. Seems like the compiled classes are missing on the disc even though I see there are not errors in the test class.
I think we can take this up when are in good position with feature implementation in Javac branch compared to JDT. Then we can look at improving the the times.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I know this is too early to test and measure with javac implementation. But anyway I just wanted to see how it goes.
I was trying to load the https://github.com/Azure/azure-sdk-for-java in VSCode for debugging an issue. When I try to load this project with JDT it takes around ~ 10min or less with project 2K errors. When I try to load the same with Javac it takes around more than 15min with 10k project errors.
I think project errors are due to something I'm missing to do prior to importing. But the time it takes to run the import has a huge difference and also the responsiveness of VSCode.
Also in JDT mode regardless I had 2K errors, I could run some of unit tests and work with the code base. But in Javac mode the same tests cannot be executed since the java-debug fails to find the compiled classes. Seems like the compiled classes are missing on the disc even though I see there are not errors in the test class.
I think we can take this up when are in good position with feature implementation in Javac branch compared to JDT. Then we can look at improving the the times.
Beta Was this translation helpful? Give feedback.
All reactions