trellis-ldp / camel-ldp-recipes

A collection of LDP-based workflows for use with Apache Camel
Apache License 2.0
4 stars 0 forks source link

Bump jakarta.xml.bind:jakarta.xml.bind-api from 2.3.3 to 4.0.2 #339

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps jakarta.xml.bind:jakarta.xml.bind-api from 2.3.3 to 4.0.2.

Release notes

Sourced from jakarta.xml.bind:jakarta.xml.bind-api's releases.

Jakarta XML Binding API 4.0.1

The 4.0.1 release is a bug fix release of 4.0.0.

Following changes are included:

  • #240 - Fixes parseBoolean according spec
  • #273 - Allow usage of API jar on Android platform
  • #275 - Make sure providers get only properties they are required to understand
  • #276 - Add instructions for OSGi mediator
  • uses Jakarta Activation APIs 2.1.2

New Contributors

Full Changelog: https://github.com/jakartaee/jaxb-api/compare/4.0.0...4.0.1

Jakarta XML Binding API 4.0.0

The major release contains following changes:

  • drops compatibility with JAXB 1.0
  • removes constraints on using java.desktop/java.beans.Introspector
  • removes deprecated jakarta.xml.bind.Validator
  • removes deprecated jakarta.xml.bind.context.factory property
  • drops implementation lookup through META-INF/services/jakarta.xml.bind.JAXBContext
  • drops implementation lookup through jaxb.properties file
  • adds implementation lookup through the properties Map passed to JAXBContext.newInstance(...) methods
  • provided implementation of the DatatypeConverterInterface throws exception on invalid input

Project Board: https://github.com/eclipse-ee4j/jaxb-api/projects/1 Full Changelog: https://github.com/eclipse-ee4j/jaxb-api/compare/3.0.0...4.0.0

Jakarta XML Binding API 4.0.0 RC2

The 4.0.0 RC2 is a second release candidate of 4.0.0.

Following changes are included:

Jakarta XML Binding API 4.0.0 RC1

The 4.0.0 RC1 is a first release candidate of 4.0.0.

Following changes are included:

Jakarta XML Binding API 3.0.1

The 3.0.1 release is a bug fix release of 3.0.0.

Following changes are included:

... (truncated)

Commits


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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[bot] commented 8 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.