They are not required if you use the command line interface, but I find that they do make things easier since I can run the gradle command from Eclipse directly.
The instructions mention that if you import through gradle, you will need to replace the Eclipse files with the ones in the repo because at this point gradle still messes them up. On Mon, Aug 17, 2020 at 10:43 AM Tom Schindl <tom.schi...@bestsolution.at> wrote: > Hi, > > Do we really use the Eclipse-Gradle-Tooling now? I think the reasons we > checked in all .product/.classpath files is that this did not work in > the past. > > At least my Eclipse install I use for OpenJFX-Development does not have > the gradle-tooling installed and things work there just fine. > > Tom > > Am 16.08.20 um 21:49 schrieb Nir Lisker: > > Hi Andrew, > > > > I did the same setup only with Ubuntu 18, which shouldn't matter, and I > > don't remember having this issue. I can try redoing it next time I boot > the > > Ubuntu partition. > > > > What looks odd is that the error references the build directory. What > > happens if you clean the project first? > > > > - Nir > > > > On Sat, Aug 15, 2020 at 1:55 PM Andrew Waters <gb91...@gmail.com> wrote: > > > >> Hi All, > >> > >> > >> I'm trying to diagnose a bug in OpenJFX that I've been struggling with > >> on and off for almost a year(!) and I decided to build OpenJFX from > >> source and use Eclipse to help. I've built a brand new Ubuntu > >> 20.04.1-Desktop system with OpenJDK 14.0.1 and the latest stable OpenJFX > >> 14. I've run the Gradle build and run the tests and all looks 100%. > >> > >> > >> When importing the root directory (home/jdkdev/dev/jfx) into Eclipse > >> using the gradle import tool (using the wrapper option as recommended) I > >> get this build path error: > >> > >> > >> Cannot nest > >> > 'home/jdkdev/dev/jfx/modules/javafx.base/build/classes/java/main/javafx.base' > >> > >> inside library > >> 'home/jdkdev/dev/jfx/modules/javafx.base/build/classes/java/main' > >> > >> > >> It seems to be trying to set up a looped import to itself somehow. I've > >> tried to edit the build path in eclipse but the fields appear to be all > >> non-editable. Has anyone any idea as to what the problem is and how to > >> fix it? Has anyone recently done a successful import with these latest > >> levels? > >> > >> > >> As this is the base module none of the other modules compile of course > >> so they too may have other problems once the base module is fixed. > >> > >> > >> I tried the "existing projects" import too but that just appears to have > >> even more problems. > >> > >> > >> Thanks, > >> > >> Andrew Waters > >> > >> UK. > >> > >> >
