XML Resolver v4.2.0

This release fixes a couple of small bugs and adds new configuration features:

1. CACHE_ENABLED can be explicitly set false to disable all caching.
2. SAXPARSERFACTORY_CLASS and XMLREADER_SUPPLIER can configure the resolver to construct a new parser without relying on JAXP global defaults.
3. The XML Resolver Data jar now includes a resource that does not exist on the web: https://xmlresolver.org/data/resolver/succeeded/test/check.xml If this URI resolves successfully, you can be sure that the data jar is on the classpath and is being used.
4. Manifest improvements proposed by @aanno fix problems under Java 9+.

What's Changed

• added Automatic-Module-Name to manifests by @aanno in #85
• New tests by @ndw in #87
• Add an explicit cache-enabled property by @ndw in #88
• Fix the copy constructor; add new tests by @ndw in #90
• Add SAXPARSERFACTORY_CLASS and XMLREADER_SUPPLIER features by @ndw in #92
• Release XML Resolver 4.2.0 by @ndw in #93

New Contributors

• @aanno made their first contribution in #85

Full Changelog: 4.1.2...4.2.0

4.1.2

XML Resolver 4.1.2 released

XML Resolver version 4.1.1

What's Changed

• Fix Windows issues by @ndw in #83
  Full Changelog: 4.1.0...4.1.1

4.1.0

XML Resolver 4.1.0 released

XML Resolver version 4.0.0

This release contains two new features, improved (or at least simplified) logging and support for JAXP 185.

I've bumped it to 4.0.0 because the logging changes are backwards incompatible. To get the old behavior, you must explicitly select the SystemLogger using the ResolverFeature.RESOLVER_LOGGER_CLASS.

What's Changed

• Refactor to make logging behavior simpler for users by @ndw in #77
• Implement JAXP 185 support by @ndw in #78
• JavaDoc improvements by @ndw in #79

Full Changelog: 3.1.8...4.0.0

XML Resolver version 3.1.8

This release fixes a bug (#72) where an IllegalArgumentException thrown by the java.net.URI class was not correctly caught.

I've also added a feature where, if, for example, you're working with the resolver at a lower level in your own API, you can configure it to throw those exceptions. This will save you from having to test for invalid URIs independently, if you care.

What's Changed

• Catch IllegalArgumentException, add THROW_URI_EXCEPTIONS feature by @ndw in #74

Full Changelog: 3.1.7...3.1.8

XML Resolver version 3.1.7

This release adds a getCatalogResolver() method to the Resolver. This allows a user to get access to more detailed information about resource resolution. (Where the Resolver object returns the types required by the APIs it implements, CatalogResolver returns a resource description.)

XML Resolver version 3.1.6

This release, like 3.1.5, is really a release to update the data jar. There are a few build improvements behind the scenes, but those don't have any impact on the release artifacts.

What's Changed

• Republish resolver to get latest data by @ndw in #67

Full Changelog: 3.1.5...3.1.6

3.1.5

XML Resolver 3.1.5 released

XML Resolver verison 3.1.4

This release contains no code changes, it just updates the Maven-published release of the data jar to 0.0.5.

What's Changed

• Bump the data version to 0.0.5 by @ndw in #62
• Release version 3.1.4 by @ndw in #63

Full Changelog: 3.1.3...3.1.4