JPMS modularization and more modern Java

[Oliver-Loeffler]

Hi @aashideacon,

as proposed I've implemented new versions fo FXFileChooser which make use of Java module system, hence each of the new releases contains a module-info. The only significant difference between 0.0.9 and 0.0.10 is the use of Java modules and the newer JavaFX/Java versions.

There are now following versions available for testing (I hope thre are not too many flaws):

Java	JavaFX	artifact version
8	8	0.0.9
9	9	0.0.10-jdk9
11	11.0.1	0.0.10-jdk11
11	16	0.0.10-jdk16
17	17	0.0.10-jdk17

Would be happy to hear your opinion and feedback on this. Hope this helps.
Release coordinates at http://search.maven.org are:

JDK9

<dependency>
  <groupId>net.raumzeitfalle.fx</groupId>
  <artifactId>filechooser</artifactId>
  <version>0.0.10-jdk9</version>
</dependency>

JDK11 (LTS)

<dependency>
  <groupId>net.raumzeitfalle.fx</groupId>
  <artifactId>filechooser</artifactId>
  <version>0.0.10-jdk11</version>
</dependency>

JDK11 with OpenJFX16:

<dependency>
  <groupId>net.raumzeitfalle.fx</groupId>
  <artifactId>filechooser</artifactId>
  <version>0.0.10-jdk16</version>
</dependency>

JDK17 with OpenJFX17:

<dependency>
  <groupId>net.raumzeitfalle.fx</groupId>
  <artifactId>filechooser</artifactId>
  <version>0.0.10-jdk17</version>
</dependency>

I've already seen that due to how TestFX works, a restructuring of the project will help. Eventually all tests will be moved into a sub-project which will not get packaged. Tests can run on module path and if useful on classpath.

[Oliver-Loeffler]

Project is now modularized and test have been moved into separate sub-project.