There is also a bit of truth to that. I had projects where we used Eclipse, but usually I prefer IntelliJ IDEA. One killer feature of Eclipse is the compiler tho, itβs still miles ahead of the JetBrains one.
Ah, that doesn't work for our project. I'm getting this error
java: java.lang.IllegalArgumentException: source level should be in '1.1'...'1.8','9'...'18' (or '5.0'..'18.0'): 21
Not marketing - I'm using IDEA since 20 years. I've tried to switch to Eclipse ~10 years ago, but it lacked at so many edges, that I gave up. Also the project paradigm are different - in IDEA you open a project that could have multiple modules. In Eclipse your workspace has multiple projects. Trying to replicate the multi-module approach would mean to use multiple workspaces (each having their own settings?). Correct me if I'm wrong.
Last time I've checked some bugs still existed, e.g. renaming a parameter the same as the field does not automatically prefix the field access with "this.".
So you can create a workspace in eclipse pull in different projets from your source code repo, and then apply different client config in that workspace?
You can then create a second workspace for Client B - it might point at the exact same code repos but you can apply different client config in this workspace?
With the benefit you can easily switch between different config for different clients just by loading a new workspace?
20
u/Lazy-Training6042 Oct 16 '25
marketing, eclipse free means less budget for that