Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

Bump xmlunit-matchers from 2.6.2 to 2.8.1 #77

Conversation

dependabot-preview[bot]
Copy link

Bumps xmlunit-matchers from 2.6.2 to 2.8.1.

Release notes

Sourced from xmlunit-matchers's releases.

XMLUnit for Java 2.8.1

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.

XMLUnit for Java 2.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:

  • changed optional JAXB dependency to use Jakarta XML Binding API PR #186 by @endrejeges

  • 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.
  • added a new extractingText method to MultipleNodeAssert to make it possible to write AssertJ assertions against the textual content of nodes more easily. Issue #192 and PR #193 by @keesvandieren

  • 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).

  • DefaultNodeMatcher with multiple ElementSelectors could fail to find the best matches as the order of ElementSelectors should select them. #197

  • Input builder now supports java.nio.file.Path #196

  • It is now possible to specify a custom TransformerFactory for DefaultComparisonFormatter. #195

XMLUnit 2.7.0

The biggest changes are to the placeholder and assertj modules. The assertj module should now work with AssertJ 3.15+.

This version contains a backwards incompatible change to the PlaceholderHandler interface that is part of the experimental placeholders module: The evaluate method now receives a variable number of string arguments in addition to the textual content of the element/attribute. This allows placeholders like ${xmlunit.matchesRegex(some\s*regex)}.

Changelog

Sourced from xmlunit-matchers's changelog.

XMLUnit for Java 2.8.1 - /Released 2020-11-15/

  • 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.

XMLUnit for Java 2.8.0 - /Released 2020-10-30/

  • changed optional JAXB dependency to use Jakarta XML Binding API PR #186 by @endrejeges

  • 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.
  • added a new extractingText method to MultipleNodeAssert to make it possible to write AssertJ assertions against the textual content of nodes more easily. Issue #192 and PR #193 by @keesvandieren

  • 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).

  • DefaultNodeMatcher with multiple ElementSelectors could fail to find the best matches as the order of ElementSelectors should select them. #197

Commits
  • 4f40e46 cut XMLUnit 2.8.1
  • 36470a1 document xmlunit-assertj3 module. closes #203
  • d62805d migrated to travis-ci.com
  • 7da8ed8 update javadocs for xmlunit-assertj3
  • 39e8e9a update release notes for #203
  • a1b5ea4 Merge pull request #206 from rigd-loxia/main
  • cfec6b1 #205: escape '%'-signs for further handling in assertj.
  • 6e1f83d Use the now protected isElementOfCustomAssert, see #203
  • 70df913 hello is the expanded reference, nit xyzzy
  • 18e329e prepare for isElementOfCustomAssert becoming protected - see #203
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Nov 16, 2020
@dependabot-preview
Copy link
Author

Superseded by #81.

@dependabot-preview dependabot-preview bot deleted the dependabot/maven/org.xmlunit-xmlunit-matchers-2.8.1 branch December 22, 2020 03:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants