This release fixes OSGi headers inside xmlunit-core's and xmlunit-legacy's manifests, it doesn't contain any other changes.

Full list of changes:

• marked OSGi Import-Package optional for javax.xml.bind packages in xmlunit-core.
  Also fixed the Export-Package header of the legacy module.
  Issue #300
  PR #301

This release fixes a problem with the published POM of the xmlunit-legacy module. It doesn't contain any changes to any of the other modules.

• placeholders can now also be used inside of the local part of xsi:type attributes.
  PR #293

• PlaceholderDifferenceEvaluator would cause ClassCastException for documents with
  differences in xsi:type attributes.
  Issue #276

• updated a bunch of Maven plugins, in particular we now create CylcloneDX files using
  version 1.6 of the schema.
  PR #292

• updated bytebuddy dependency of xmlunit-assertj to 2.12.23 in order
  to support Java 17 properly

• Migrated form TraciCI to CircleCI
  Issue #289

• Migrated to Sonatype's Central Portal
  Issue #287

• added a new BOM artifact xmlunit-bom
  Issue #269

• Comparison has earned a new convenience constructor.
  PR #280 by
  @hiufung-kwok

• Input.from now detects Reader arguments and uses fromReader.
  PR #281 by
  @SThomasP

• add a new ElementSelectors.byNameAndAllAttributes variant that filters attributes before deciding whether elements can be compared.
  Inspired by Issue #259

• By default the TransformerFactorys created will now try to disable extension functions. If you need extension functions for your transformations you may want to pass in your own instance of TransformerFactory and TransformerFactoryConfigurer may help with that.
  Inspired by Issue #264

• JAXPXPathEngine will now try to disable the execution of extension functions by default but uses XPathFactory#setProperty which is not available prior to Java 18. You may want to enable secure processing on an XPathFactory instance you pass to JAXPXPathEngine instead - and XPathFactoryConfigurer may help with that.

• fixed some AssertJ tests that didn't work on Windows.
  Issue #252 and PR #253 by @Boiarshinov

• added overloads to ElementSelectors.byXPath that accept a XPathEngine argument.
  Issue #255

• added Cyclone DX SBOMs to release artifacts

The major change of XMLUnit for Java 2.9.0 is the addition of a new module xmlunit-jakarta-jaxb-impl that can be used in addition to xmlunit-core when you want to use the Jakarta XML Binding API in version 3. For details please see the user's guide.

The full list of changes of XMLUnit for Java 2.9.0 is:

• added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the User's Guide.

  This change is not fully backwards compatible. The JaxbBuilder class has become abstract and the withMarshaller method has changed its signature. For most cases the change will not be noticed and for almost all other cases it should be enough to re-compile your code against XMLUnit 2.9.x.

  Issue #227 and PR #247

• added NodeFilters#satisfiesAll and satifiesAny methods to make it easier to combine multiple node filters. added to simplify the use case of #249

XMLUnit for Java 2.8.4 improves performance when comparing documents with many sibling elements.

Changelog:

• improved comparison performance for documents with many siblings
  based on a suggestion by @gerpres made in #236

• added a new fullDescription method to Diff that provides a string-representation of all differences - not just the first one like toString does.
  PR #235 fixing #232 by @Boiarshinov

• made sure AssertJ's methods to override the assertion message like withFailMessage are honored.
  #225

• adjusted unit tests so they pass when AssertJ 3.19.0 is used.
  PR #212 by mmathesius

This release fixes a bug in the new AssertJ 3.x module.

• CompareAssert inside the AssertJ3 module swapped the expected and
  actual parameters when creating the assertion error.
  #210 by @f-lopes

The only real change when compared to XMLUnit for Java 2.8.0 is the introduction of a new xmlunit-assertj3 module 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-assertj module 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 CompareAssert will no longer throw a JUnit 4.x ComparisonException but an opentest4j AssertionFailedError instead.

  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.

  Many thanks to @Zegveld, @scordio and @joel-costigliola.