Global announcements

docx4j 8.3.7 was uploaded to Maven Central yesterday. Being in the 8.x series, minimum supported Java version is 8.0. Please note that 8.x is now a legacy branch; users are encouraged to migrate to v11.4 where active development is taking place.

8.3.7 is a recommended update for anyone using v8.3.2, v.8.3.3 or 8.3.4, since it corrects an issue preventing documents containing certain chart parts from saving.

It also brings parity with 11.4.7 (hence the .7 ...

docx4j 11.4.7 is now available in Maven Central. For downloads, go to https://www.docx4java.org/downloads.html

The logic behind the version number is as follows:
- its docx4j 11 since it targets Java 11; If you are not using Java 11 or later, you should stick with docx4j 8.3.4 (compiled for Java 8).
- it is docx4j 11.4, not 11.3, since this release uses jakarta.xml.bind (as opposed to the previous javax.xml.bind)

Since ...

docx4j-ImportXHTML 11.4.6 is now available in Maven Central. For downloads, go to https://www.docx4java.org/downloads.html

This release is JPMS modularised, and uses jakarta.xml.bind.

The logic behind the version number is as follows:
- its -ImportXHTML 11 since it targets Java 11; If you are not using Java 11 or later, you should stick with ImportXHTML 8.3.2 (compiled for Java 8).
- it is -ImportXHTML 11.4, since like docx4j 11.4, this release ...

docx4j 11.4.6 is now available in Maven Central. For downloads, go to https://www.docx4java.org/downloads.html

The logic behind the version number is as follows:
- its docx4j 11 since it targets Java 11; If you are not using Java 11 or later, you should stick with docx4j 8.3.4 (compiled for Java 8).
- it is docx4j 11.4, not 11.3, since this release uses jakarta.xml.bind (as opposed to the previous javax.xml.bind)

Since ...

docx4j 11.4.5 is now available in Maven Central.

For downloads, go to https://www.docx4java.org/downloads.html

The logic behind the version number is as follows:
- its docx4j 11 since it targets Java 11; If you are not using Java 11 or later, you should stick with docx4j 8.3.4 (compiled for Java 8).
- it is docx4j 11.4, not 11.3, since this release is the first to use jakarta.xml.bind (as opposed to ...

docx4j 8.3.4 is now in Maven Central. Being in the 8.x series, minimum supported Java version is 8.0.

This is a minor release, addressing some font related issues in docx to PDF via XSL FO output in v8.3.3 (released last week). Anybody contemplating v8.3.3 should use this v8.3.4 instead.

It also bumps FOP to v2.7.

To use docx4j 8.3.4 via Maven, just add one and only one of docx4j-JAXB-Internal, docx4j-JAXB-MOXy,
or docx4j-JAXB-ReferenceImpl to your pom. ...

This post is about the Log4j vulnerability recorded at
https://cve.mitre.org/cgi-bin/cvename.c ... 2021-45046

You should determine whether your application is using log4j, and if so, address the documented risk.

By way of background, in v3 of Nov 2013, docx4j switched from log4j to slf4j. This means that for docx4j 3.0 onwards, the choice of logging implementation has been up to you: you could choose to use log4j, or eg logback ...

docx4j 8.3.2 and 11.3.2 are now in Maven Central.

8.3.2 is a minor release (compared to 8.3.1); 11.3.2 is more significant (compared to the last 11.x release which was 11.2.9).

11.3.2 is a JPMS modularised release for Java 11 users, and brings the 11.x series to parity with 8.3.2.

Changes in Version 8.3.2

+ ChartEx (eg the newish statistical, hierarchy and combo charts) changes so Word can open output, fixes #481

+ When saving as ...

docx4j 8.3.1 is now in Maven Central.

This is a minor release, but fixes an issue in 8.3.0 affecting those using 8.3.x with docx4j-ImportXHTML.

Other changes in Version 8.3.1

+ Concurrency fix in NamespacePrefixMapper (most obvious with MOXy); fixes #464

+ PDF via FO: Output hyphenate, language and country attributes to support hyphenation in PDF output

+ Move legacy PDF converter out of docx4j-core (to new module docx4j-legacy-service), so -core no longer requires Apache HttpComponents ...

docx4j 8.3.0 is now in Maven Central.

The main change in this release is that the font discovery code, used in PDF via FO and borrowed from Apache FOP, is refreshed from recent FOP source code. This allows a number of fonts which previously couldn't be read to be read successfully.

Since this change introduces several new dependencies (fontbox and fop-events), we have started the 8.3 version series.

Notable changes in Version 8.3.0

- PDF ...