Docx4j 8.0 (or 6.2??) release planning
Posted: Wed Apr 03, 2019 1:44 pm
The next significant version of docx4j is now nearing release.
At issue is whether to target Java 6 or Java 8?
The release contains the following significant changes:
1. its now a Maven multi-module project
2. the way we handle alternative JAXB implementations has changed to make it easier to use docx4j in various environments:
- the Oracle JRE "internal" JAXB implementation should "just work".
- If you want to use the JAXB Reference Implementation you add docx4j-JAXB-ReferenceImpl to your classpath .
- If you want to use MOXy, add docx4j-JAXB-MOXy
3. we repackage Xalan; docx4j uses its repackaged version
The work is in branch https://github.com/plutext/docx4j/tree/ ... _0_0_MULTI
And we're also looking to make it OSGi friendly.
This release is in preparation for a docx4j 11 (or 9) which would require Java 11 (or possibly only 9). Docx4j 11 is currently waiting on https://github.com/eclipse-ee4j/jaxb-ri to release a Java 11 friendly JAXB 2.4.0 to Maven Central.
Anyway, the question for now is whether this release should target Java 6 or Java 8?
In favour of naming it docx4j 6.2, targeting Java 6:
- the release would compile for Java 6, so why not?
In favour of naming it docx4j 8, targeting Java 8:
- we can bump the deps to versions which require min Java 8
- avoid maintaining a v6.2 which is quite a bit different from v6.1.2
I'm leaning towards a docx4j 8 targeting Java 8, but if you have strong feelings, please provide feedback here.
Naturally, the next Docx4j Enterprise Release will be aligned.
thanks .. Jason
At issue is whether to target Java 6 or Java 8?
The release contains the following significant changes:
1. its now a Maven multi-module project
2. the way we handle alternative JAXB implementations has changed to make it easier to use docx4j in various environments:
- the Oracle JRE "internal" JAXB implementation should "just work".
- If you want to use the JAXB Reference Implementation you add docx4j-JAXB-ReferenceImpl to your classpath .
- If you want to use MOXy, add docx4j-JAXB-MOXy
3. we repackage Xalan; docx4j uses its repackaged version
The work is in branch https://github.com/plutext/docx4j/tree/ ... _0_0_MULTI
And we're also looking to make it OSGi friendly.
This release is in preparation for a docx4j 11 (or 9) which would require Java 11 (or possibly only 9). Docx4j 11 is currently waiting on https://github.com/eclipse-ee4j/jaxb-ri to release a Java 11 friendly JAXB 2.4.0 to Maven Central.
Anyway, the question for now is whether this release should target Java 6 or Java 8?
In favour of naming it docx4j 6.2, targeting Java 6:
- the release would compile for Java 6, so why not?
In favour of naming it docx4j 8, targeting Java 8:
- we can bump the deps to versions which require min Java 8
- avoid maintaining a v6.2 which is quite a bit different from v6.1.2
I'm leaning towards a docx4j 8 targeting Java 8, but if you have strong feelings, please provide feedback here.
Naturally, the next Docx4j Enterprise Release will be aligned.
thanks .. Jason