The Run panel rely on a launch.json file, and it can be saved on your git repository if you want to share it with team-workers. There is also an equivalent of the Run Configuration with the Run panel to fire your project.

You still have auto-completion and JavaDoc is shown when it's necessary. There is also a workspace system in VSCode to open multiple folder at once, it may be useful if you work on multiple projects at the same time (front and back for example). I do not loose anymore time to import projects, I just open the right folder. It's not a big difference but for me it is more easy to switch between projects. If some project have been removed then you will not see it anymore. VSCode is more like other editor (Atom.), and you can simply open a folder that contain your multi-modules Maven project. My main concern with this approch is around multi-modules Maven projects : once you add or remove a module, Eclipse is lost and you need to import again the missing module. This is I think the most important change between Eclipse and VSCode.Įclipse is relying on a workspace concept where you import Java projects. Globally you can relly on the Java Extension Pack that install all the main Java extensions for you. I don't want to present each extension, I found this article which is describing that very well. So the initial text editor can be compared with a fully featured IDE once the right extensions have been installed. Each extension add a little extra power to the tool. So I am still looking at Java source code project, but with a different level of usage than before. Here is my journey and a quick comparison of the tools.įirst of all I need to inform that I am actually Product Owner and not anymore a full-time developer. I use to work with Eclipse since around 2010, only for Java projects. I am working for a software editor and we mainly use Java as backend language.

Java on visual studio code