Docx4j 11.1.0 released for Java 11
Posted: Mon Jun 03, 2019 11:15 am
docx4j 11.1.0 - for use with Java 11 or later - is now available in Maven Central.
11.1.0 is our first JPMS modularised release, so the jars contain module-info.class entries.
11.1.0 is compiled with Java 12, targeting Java 11. If you are not using Java 11, you should stick with docx4j 8.1.0.
Aside from the use of named modules / module path, this release is pretty much the same as v8.1.0. However, docx4j-export-fo is temporarily omitted since FOP 2.3's avalon dependencies are not JPMS-friendly. Whem FOP 2.4 is released, we should be able to include it again.
docx4j 11.1.0 source code can be found at https://github.com/plutext/docx4j/tree/ ... ent-11.1.0
To use docx4j 11.1.0 via Maven, just add either docx4j-JAXB-MOXy
or docx4j-JAXB-ReferenceImpl 11.1.0 to your pom. https://search.maven.org/search?q=g:org.docx4j
JPMS modularisation notes
The module names correspond to our Maven modules:
org.docx4j.openxml_objects
org.docx4j.openxml_objects_pml
org.docx4j.openxml_objects_sml
org.docx4j.core
org.docx4j.JAXB_MOXy
org.docx4j.JAXB_ReferenceImpl
We require named modules:
docx4j_xalan_serializer
docx4j_xalan_interpretive
org.slf4j
(Other dependencies generally aren't JPMS-ready, so they go on the classpath in the "unnamed" module.)
11.1.0 is our first JPMS modularised release, so the jars contain module-info.class entries.
11.1.0 is compiled with Java 12, targeting Java 11. If you are not using Java 11, you should stick with docx4j 8.1.0.
Aside from the use of named modules / module path, this release is pretty much the same as v8.1.0. However, docx4j-export-fo is temporarily omitted since FOP 2.3's avalon dependencies are not JPMS-friendly. Whem FOP 2.4 is released, we should be able to include it again.
docx4j 11.1.0 source code can be found at https://github.com/plutext/docx4j/tree/ ... ent-11.1.0
To use docx4j 11.1.0 via Maven, just add either docx4j-JAXB-MOXy
or docx4j-JAXB-ReferenceImpl 11.1.0 to your pom. https://search.maven.org/search?q=g:org.docx4j
JPMS modularisation notes
The module names correspond to our Maven modules:
org.docx4j.openxml_objects
org.docx4j.openxml_objects_pml
org.docx4j.openxml_objects_sml
org.docx4j.core
org.docx4j.JAXB_MOXy
org.docx4j.JAXB_ReferenceImpl
We require named modules:
docx4j_xalan_serializer
docx4j_xalan_interpretive
org.slf4j
(Other dependencies generally aren't JPMS-ready, so they go on the classpath in the "unnamed" module.)