Skip to content

Bump domtripVersion from 0.4.1 to 0.6.0#11784

Closed
gnodet wants to merge 1 commit intomasterfrom
fix/domtrip-0.6.0-upgrade
Closed

Bump domtripVersion from 0.4.1 to 0.6.0#11784
gnodet wants to merge 1 commit intomasterfrom
fix/domtrip-0.6.0-upgrade

Conversation

@gnodet
Copy link
Contributor

@gnodet gnodet commented Mar 11, 2026

Summary

Closes #11766 — supersedes the dependabot PR by adapting code to breaking API changes.

  • Bump domtripVersion from 0.4.1 to 0.6.0
  • Adapt to 0.5.0 breaking renames: Element.child()childElement(), Element.children()childElements(), ContainerNode.removeNode()removeChild()
  • Work around missing equals()/hashCode() in Coordinates class (was a record, converted to regular class in 0.5.0 without adding them) by using toGAV() string comparison

Changes

  • pom.xml: Version bump
  • All mvnup strategy classes and tests: Renamed method calls to match new domtrip API
  • GAVUtilsTest: Use toGAV() string comparison for Coordinates equality checks
  • InferenceStrategy: Use toGAV() comparison in isParentInReactor()

Adapt code to breaking API changes introduced in domtrip 0.5.0:
- Rename Element.child() to Element.childElement()
- Rename Element.children() to Element.childElements()
- Rename ContainerNode.removeNode() to ContainerNode.removeChild()

Work around missing equals/hashCode in Coordinates class
(converted from record to class in 0.5.0 without adding them):
- Use toGAV() string comparison instead of Coordinates.equals()

Closes #11766
@gnodet gnodet closed this Mar 11, 2026
@gnodet gnodet deleted the fix/domtrip-0.6.0-upgrade branch March 11, 2026 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant