JDK-8209015: Update Eclipse project files
Nir Lisker
nlisker at gmail.com
Wed Aug 8 14:07:51 UTC 2018
Hi,
After the removal of some dependencies on JDK modules the Eclipse classpath
files should be updated to allow developers to work on Eclipse without
needing to do tricky configuration themselves. Iv'e submitted a JBS issue
[1] to track the progress.
There were discussion about removing IDE-specific files in the JBS [2] and
on GitHub (see links in JBS issue). It seems that the idea was dropped and
I propose to close this issue. A discussion on this issue can be found on
the mailing list [3].
On to the technical discussion:
Iv'e put up a gist with my classpath files [4], but Swing still gives me
problems with an NPE during the build.
On 08.08.18 08:55, Tom Schindl wrote:
> > Hi Nir,
> >
> > I currently use the attached stash to make Eclipse compile all modules.
> >
> > Unfortunately I have to modify the following java-Files to get away
> > without any compile errors:
> > * Dialog => Added a method getDialog() instead of directly accessing the
> > field
>
We have to wait for the fix [5], there's no workaround.
> > * javafx.fxml => Add a static require for controls
> > * javafx.web => Add a static require for java.management
>
> Looking once more I think read-edges are completely missing in Eclipse
> for projects. I can patch other projects to get a read-edge but not the
> project itself!
>
> In the end what we want is to patch eg the javafx.fxml-module to have a
> read-edge for javafx.control. I don't see how this can be done with the
> current Eclipse setup!
>
> My work around today is to add static-require and I don't see a way
> around that.
>
It's possible to do it in the classpath file as Iv'e shown in [6], but I
don't know if JUnit will work. I seem to have general JUnit problems. Can
you try with my files and unmodified module-info.java files and see which
projects can run JUnit? They should all compile.
The bulk of the work for modular support is tracked under [7] and they want
input from users, so try to help them. There's also a UI specific issue for
modular projects [8].
- Nir
[1] https://bugs.openjdk.java.net/browse/JDK-8209015
[2] https://bugs.openjdk.java.net/browse/JDK-8198795
[3]
http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-April/021740.html
[4] https://gist.github.com/nlisker/fd2d42f6467c069cf8c4cc054ba0ea40
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=536330
[6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=526963
[7] https://bugs.eclipse.org/bugs/show_bug.cgi?id=526831
[8] https://bugs.eclipse.org/bugs/show_bug.cgi?id=536330
More information about the openjfx-dev
mailing list