Stefan Bodewig's Weblog

Weblog Main Feeds

• de (8)
• en (311)

About Me Homepage Family Articles Talks
My PGP key
Open Hub profile
Categories Archive

With this release the dependency of xmlunit-core on the JAXB API has been marked optional. If you need the JAXB parts of XMLUnit you now must explicitly add a dependency on the API version matching your implementation. There is no other change compared to version 2.13.0.

path: /en/oss/XMLUnit | #

• oss
• XMLUnit

XMLUnit for Java 2.13.0 adds new options allowing people to strengthen the security of the XML parser used during validation or XPath evaluation and adds an option to specify the locale used to parse patterns in the isDateTime placeholder.

Full list of changes:

• added explicit settings to the Validator classes that disable (external) DTD loading during validation. The default remains to allow loading of external content as this is often a requirement during validation.
  PRs #331 and #332 by @jmestwa-coder
• added constructor overloads to JAXPXPathEngine to allow specifying the DocumentBuilderFactory used for the Source overloads of the selectNodes and evaluate methods.
  PRs #333 by @jmestwa-coder
• IsDateTimePlaceholderHandler now parses the explicit and ISO date formats using Locale.US rather than the JVM default locale so results no longer depend on the host locale. An optional second argument allows specifying a different locale as a BCP 47 language tag.
  PR #335 by @jmestwa-coder

XMLUnit.NET adds an option to specify the culture used to parse patterns in the isDateTime placeholder.

Full list of changes:

• IsDateTimePlaceholderHandler now supports an optional second argument specifying a different CultureInfo than the invariant culture used by default as CultureInfo name like de or fr-FR.
  Also modified the logic when no argument is present to still try parsing using the current culture and then trying a set of ISO patterns using the invariant culture in turn - making isDateTime match what the Java version does mor closely.
  PR #54 based on PR xmlunit/#335 by @jmestwa-coder

path: /en/oss/XMLUnit | #

• oss
• XMLUnit

This release may require you to adjust you configuration when comparing files that use DTDs. When XMLUnit 2.6.0 has been release it was intended to disallow DTD parsing by default, but due to a bug still allowed it. This has now been fixed.

Full list of changes:

• bumped xmlunit-assertj3's dependency on assert to 3.27.7.
  This is to make people aware of https://github.com/assertj/assertj/security/advisories/GHSA-rqfh-9r24-8c9r
  XMLUnit itself does not use the affected code in AssertJ so the upgrade is not strictly necessary - and this is why the xmlunit-assertj module is not updated. In fact the assertions provided by xmlunit-assertj3 are the recommended upgrade path for users of AssertJ 3.x+.
  PRs #320 and #321
• actually made withDTDParsingDisabled do what it says.
  This is a bugfix and in a way it is backwards incompatible as it changes default behavior in a way that I intended to do with XMLUnit 2.6.0 eight years ago. DocumentBuilderFactoryConfigurer.DefaultWithDTDParsing provides the behavior of XMLUnit 2.6.0 to 2.11.0.
  PRs #326 by @jmestwa-coder and #328

path: /en/oss/XMLUnit | #

• oss
• XMLUnit

At $work I use a dual boot laptop with Linux as my primary OS and Windows for the the occasional thing that really requires a real Windows installation. I've got a disk partition shared between both systems and use VeraCrypt as an encryption solution that works for both operating systems. I switched to it after VeraCrypt's predeccessor TrueCrypt was abandoned. It's been completely reliable and I'm very happy with this.

Right now it looks as if Microsoft has decided to revoke the developer account of VeraCrypt's main developer without any way for him to appeal. This is going to block creating new Windows releases as far as I understand. And it looks as if nobody had reached out to him and explained why this happened.

If you happen to know anybody inside of Microsoft who could help, maybe given them a nudge.

.

path: /en/oss | #

• oss

This release is identical to XMLUnit for Java 2.10.4 except for the dependency list of the xmlunit-jakarta-jaxb-impl modulle. If you don't use the module, you can ignore this release.

Up until XMLUnit 2.10.4 the xmlunit-jakarta-jaxb-impl module depended on org.glassfish.jaxb:jaxb-runtime making it more difficult to choose a different JAXB implementation than necessary (see #313). This dependency has now been removed.

If you use the xmlunit-jakarta-jaxb-impl module you may now need to specify the JAXB implementation you want to use explicitly. If you have excluded the module's dependency inside your own build configuration so far, you can now safely remove the exclusion.

path: /en/oss/XMLUnit | #

• oss
• XMLUnit