On Wed, 16 Sep 2026 21:54:50 GMT, Nir Lisker <[email protected]> wrote:
>>> This change will need to get backported to all the releases we currently >>> support @kevinrushforth , otherwise it's a paint to go back and forth. >> >> I don't think this is required. (But might help if we use some of the new >> features.) >> >>> Please add .classpath changes. @hjohn or @nlisker please take a look since >>> you guys use eclipse. >> >> Isn't there any way that Eclipse can derive the configuration from Gradle, >> like IntelliJ does? >> I'm always confused by all the files that Eclipse generates and are checked >> into the VCS. >> So, is there a better way to do that? For reference, in the JDK source code, >> there seem to be no Eclipse files at all. > >> Isn't there any way that Eclipse can derive the configuration from Gradle, >> like IntelliJ does? > > Not with the current broken build. It will be a nice side-effect of fixing it. > >> I'm always confused by all the files that Eclipse generates and are checked >> into the VCS. > > There are the `project` and `classpath` files that control the definition of > the project (name, type, builders, etc.) and its dependencies, respectively. > These are the main ones a project needs. Then there are the ones in > `.settings` that are used by plugins. The "core" Java plugins use them to > define endcoding, compiler versions etc. Gradle can derive most of these, but > it needs to be set up correctly. Frankly, I don't know how IntelliJ > understands that file. > >> So, is there a better way to do that? For reference, in the JDK source code, >> there seem to be no Eclipse files at all. > > Fixing the build file is the better way. The JDK doesn't keep Eclipse files, > which is why you get a lot of errors when you first get it. which you need to > fix manually. thank you @nlisker for explanations. I might add that eclipse config files do not contain absolute or user-specific paths, which eliminates the need to "configure" the workspace before it can be compiled. (I wish jfx used a single top-level eclipse project instead of multiple nested ones, but it is what it is) ------------- PR Comment: https://git.openjdk.org/jfx/pull/1925#issuecomment-5705318272
