I started to develop a Vaadin flow application. I get the following warning when I start my application. What features am I missing when not using VSCode or IntelliJ? How does the development workflow differ in eclipse? This is not clear to me, since everything seems to work. Thanks!
Hot reload… technically nothing that prevents you from developing with Vaadin (did years without it) - it just makes development more naturally… no more restarts between code chances and seeing the result.
Thank you for the info. When I save a file, my application restarts automatically, it takes a few seconds, but that is fine for me. Do you know if there are any plans to support eclipse as well?
I don’t have any insights about it. I personally don’t think there is any Eclipse Support in the near future. Eclipse and NetBeans don’t have enough market share to make the investment worth it.
I know that Eclipse does not have a huge market share anymore, although it is still used in the professional world. So it’s great to hear that it at least gets some love from the Vaadin team, I appreciate it :) I was hoping for that as well, since a Vaadin Eclipse plugin was recently updated.
Vaadin or Flow don’t need any IDE integration to work well - it’s just basic server-side Java after all. We should maybe clarify the text in that dialog to better describe whats working and what’s missing.
There are three specific optimizations that are currently only available for IntelliJ IDEA and VS Code:
Vaadin can help you set up Hotswap Agent for faster updates to Java code changes. You can do this for Eclipse by manually following the steps from that dialog.
Automatic recompile when Copilot has made changes to Java files. Without this, Eclipse will recompile changed Java files only when you move focus back to the IDE. This is an issue only when using Copilot since it updates Java files when you interact with it through the browser.
Undo and redo through Copilot needs to integrate with the undo and redo functionality in the IDE to avoid “merge conflicts”.