chore(deps): update dependency org.xmlresolver:xmlresolver to v5.3.3 #1363
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2.2->5.3.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
xmlresolver/xmlresolver (org.xmlresolver:xmlresolver)
v5.3.3Compare Source
This is the 5.3.3 maintenance release.
It fixes issue #242. Also, since the previously published 5.x maintenance release,
v5.3.2Compare Source
v5.3.1Compare Source
v5.3.0Compare Source
This is the 5.3.0 release.
v5.2.5Compare Source
This is a maintenance release of the 5.x resolver.
The following changes are included:
Fix namespace-based lookup in the DOM
The LSResourceAdapter API used when resolving documents for the DOM did not correctly handle XML Schema validation. It was failing to lookup based on the namespace. This closes issue #180.
Improved support for concurrency
The catalog lookup code was not sufficiently careful about multi-threaded access. My thanks to JFK-DXML for the patch. This closes issue #182.
A number of smaller issues (testing and build system issues and issues not expected to be user visible) have also been corrected. See the commit log for more details.
v5.2.4Compare Source
This is a maintenance release to fix a Windows-only bug related to attempting to resolve documents with "Windows path" URIs, that is, invalid URIs with backslash characters in them.
The bug (#184) was that when the URI wasn't resolved via the catalog and the resolver attempted to open the URI directly to return it, the backslashes weren't fixed and
java.net.URIthrew an exception. That's been fixed.I've also changed how the
FIX_WINDOWS_SYSTEM_IDENTIFIERSfeature is interpreted. It's now treated the same on all platforms where it was previously ignored on non-Windows platforms.These fixes have also been applied to the "v6" code on the main branch, but I have a number of other bugs to sort out before I can make a new release there.
v5.2.3Compare Source
This release fixes bug #156 where the resolver would throw an NPE if no class loader is available.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.