XMLUnit v2.8.1 Release NotesRelease Date: 2020-11-15 // 12 days ago
✅ The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new
xmlunit-assertj3module that requires AssertJ 3.18.1 or later in order to address a problem with running AssertJ tests in an OSGi environment.
👍 The original
xmlunit-assertjmodule will still be supported.
The full changelog of XMLUnit for Java 2.8.1
➕ added a new xmlunit-assertj3 module that requires AssertJ 3.18.1 or later.
🛠 This module no longer uses AssertJ internal classes that are not exported to OSGi environments and thus fixes issue #203.
📦 The module (like AssertJ 3.x itself) requires Java 8 at runtime and is similar to xmlunit-assertj but is no drop-in replacement. It uses a different Java package from xmlunit-assertj and
CompareAssertwill no longer throw a JUnit 4.x
ComparisonExceptionbut an opentest4j
🚀 The existing xmlunit-assertj module will still be supported in future releases but expect AssertJ 3.x specific changes to only get applied to xmlunit-assertj3.
Previous changes from v2.8.0
🚀 This release now requires Java 7 for all modules and updates some dependencies - the changed JAXB dependency is a breaking change. It also fixes a few bugs.
Details of changes:
⬆️ bumped the bytebuddy dependency to 1.10.10 for the AssertJ module in the hope it would help with #188
- and change its scope from provided to compile time, which should finally fix the issue.
🔄 changed the minimum Java version required from Java 6 to Java 7 for all modules (it has already been Java 7 for the AssertJ module before).
ElementSelectors could fail to find the best matches as the order of
Inputbuilder now supports
0️⃣ It is now possible to specify a custom