Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

chore(deps): update dependency org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to v0.15.1 #45

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 8, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin 0.7.4 -> 0.15.1 age adoption passing confidence

Release Notes

highsource/maven-jaxb2-plugin

v0.15.1: Release

Compare Source

What's Changed

New Contributors

Full Changelog: highsource/jaxb-tools@0.14.0...0.15.1

v0.14.0: Version 0.14.0

Compare Source

Release notes:

Development:

  • The plugin must now be built on JDK 9.

Backwards compatibility:

  • maven-jaxb2-plugin now uses JAXB 2.3 by default.
  • Java 1.6 is no longer supported.

v0.13.3: Version 0.13.3

Compare Source

Release notes:

v0.13.2

Compare Source

v0.13.1

Compare Source

v0.13.0: Version 0.13.0

Compare Source

Release notes:

  • Issues, fixed in this release.
  • Fixes #​33 - corrected lifecycle-mapping-metadata.xml for m2e in maven-jaxb20-plugin, maven-jaxb21-plugin, maven-jaxb22-plugin. The maven-jaxb2-plugin was fine.
  • Improved command-line messages (see issue #​36).
  • Added useActiveProxyAsHttpproxy configuration parameter, which, if set to true, passes active proxy from Maven settings to XJC (see #​58 and #​50).
  • The plugin now atomatically adds if-exists="true" to the generated episode files (see #​41, #​55).

Development:

  • The plugin can now be built on JDK 8 (see #​37).

Backwards compatibility:

  • The plugin now atomatically adds if-exists="true" to the generated episode files by defaults. This may cause backwards-incompatible behaviour. You can turn this off by setting addIfExistsToEpisodeSchemaBindings to false.

Many thanks to Stephan Schroevers (@​Stephan202) for his contribution.
Also many thanks to David Santos (@​Dawuid) for his work on issue #​50.

v0.12.3: Version 0.12.3

Compare Source

This release contains a number of small fixes and improvements.

No known backwards compatibility issues.

  • #​29 - use SLF4J for logging.

v0.12.2: Version 0.12.2

Compare Source

In this release:

  • Fixes a NPE in the MavenCatalogResolver (#​27)
  • Moved to the org.glassfish JAXB artifacts (#​25)
  • Closed "You should follow the trademark rules of Apache Software Foundation" (#​26) as won't fix. As renaming will damage the community, I will not rename the plugin unless legally or technically forced to.

v0.12.1: Version 0.12.1

Compare Source

New features:

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.

v0.12.0: Version 0.12.0

Compare Source

  • This version fixes a bug in the Maven catalog resolver (see Issue #​23).
  • Logging in the Maven catalog resolver was slightly improved.

v0.11.0: Version 0.11.0

Compare Source

Updated to use the newly released JAXB 2.2.11.

v0.10.0: Version 0.10.0

Compare Source

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.

v0.9.1

Compare Source

v0.9.0

Compare Source

v0.8.3

Compare Source

v0.8.2

Compare Source

v0.8.1

Compare Source

v0.8.0

Compare Source


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/org.jvnet.jaxb2.maven2-maven-jaxb2-plugin-0.x branch 2 times, most recently from dde8bc6 to e0bd9e8 Compare August 8, 2021 02:51
@renovate renovate bot force-pushed the renovate/org.jvnet.jaxb2.maven2-maven-jaxb2-plugin-0.x branch 3 times, most recently from d2cfc33 to 5398a46 Compare August 25, 2021 05:03
@renovate renovate bot force-pushed the renovate/org.jvnet.jaxb2.maven2-maven-jaxb2-plugin-0.x branch from 5398a46 to 33b260f Compare September 10, 2021 14:34
@renovate renovate bot force-pushed the renovate/org.jvnet.jaxb2.maven2-maven-jaxb2-plugin-0.x branch from 33b260f to c8ace5c Compare November 7, 2021 21:30
@renovate renovate bot force-pushed the renovate/org.jvnet.jaxb2.maven2-maven-jaxb2-plugin-0.x branch from c8ace5c to b3f9518 Compare May 16, 2022 01:32
@renovate renovate bot changed the title chore(deps): update dependency org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to v0.14.0 chore(deps): update dependency org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to v0.15.1 May 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant