Ready for Java9?

[danielpeintner]

Recently JDK9 was released and it seems the (auto)module systems breaks exificient usage.

The problem relates to the fact that "exificient" has dependencies on "exificient-core", "exificient-grammars" and such which use the same package name...

Also, according to http://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html it seems useful to add Automatic-Module-Name` entry in MANIFEST already now.

[danielpeintner]

Related w.r.t Maven and "Older projects with module-info" (see https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html)

[danielpeintner]

Issue EXIficient/exificient-core#5 (comment) mentions that

leads to a package conflict, because exificient-core and exificient itselft are containing the same package names

I assume this conflicts with Java9 module rules as well...

[danielpeintner]

For JAVA9 and OSGI PR we need different (non-conflicting) package names for each EXIficient project and its extensions such as exificient-gui, exificient-for-json and exificient-for-css.

The proposal would be to use the following naming(-convention)

com.siemens.ct.exi.exificient
com.siemens.ct.exi.exificient_core
com.siemens.ct.exi.exificient_grammars
com.siemens.ct.exi.exificient_gui
com.siemens.ct.exi.exificient_json
com.siemens.ct.exi.exificient_css

OR

com.siemens.ct.exi.default or main (default is not a valid Java identifier)
com.siemens.ct.exi.core
com.siemens.ct.exi.grammars
com.siemens.ct.exi.gui
com.siemens.ct.exi.json
com.siemens.ct.exi.css

Any feedback/proposal is welcome

-- Daniel

[danielpeintner]

With the working branches
https://github.com/EXIficient/exificient-core/tree/java9
https://github.com/EXIficient/exificient-grammars/tree/java9
https://github.com/EXIficient/exificient/tree/java9

Java9 support seems to work.

Anyhow, using module-info.java to create a Java9 module seems to report issues related to xercesImpl

... module reads package org.w3c.dom.html from both xercesImpl and xml.apis

Not sure how to fix these issues?

[danielpeintner]

version "1.0.0-SNAPSHOT" implements the afore mentioned changes with Java9 support.

[danielpeintner]

I think we can close this issue now.. Travis tests run at the moment already with JDK10 (see https://travis-ci.org/EXIficient/exificient)