Releases: highsource/jaxb-tools
Releases · highsource/jaxb-tools
Version 0.12.2
In this release:
Version 0.12.1
New features:
- This release primarily addresses up-to date checks and issue #22 in particular.
- See the documentation on the up-to date checks.
- As of this release, the usage of
forceRegenerate=true
is discouraged.
Backwards compatibility notes:
- Despite massive changes in the up-to-date check this must be backwards-compatible to previous releases.
- You may notice differences if you're compiling directly from Web resources (absolute
http
/https
URLs, which is not recommended anyway) or from JAR files. These types of resources were previously not checked for actuality during the up-to-date check.
Version 0.12.0
- This version fixes a bug in the Maven catalog resolver (see Issue #23).
- Logging in the Maven catalog resolver was slightly improved.
Version 0.11.0
Updated to use the newly released JAXB 2.2.11.
Version 0.10.0
Backwards compatibility:
- This release contains a workaround for JAXB-1044. By default, catalog resolver will be also applied to the "root" URI - that is, to the schemas you compile directly, not just to the imported or included schemas.
- This release contains a workaround for JAXB-1045. Catalog resolver will resolve the schema into the underlying resource, but it will not change the system id (URL or location) of the schea. This may result in old bindings stopped working - in case they were applied to the resolved system id instead of the original one. This would have been fixed with JAXB-1046, but there's no workaround for that as this code is not accessible from the outside.
- With the implementation of issue #5, bindings, which were bound to the file URLs of the Maven artifacts will not work anymore. You have to bind to the
maven:groupId:artifactId:type:classifier:version!/resource
from now on.