-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for jaxb3 #199
Comments
BTW, I've successfully upgraded jaxb-visitor plugin to JAXB v3 (in internal fork), using current maven-jaxb2-plugin-testing v0.14.0. The only problem I experience is
UPD: jaxb2-basics uses current version for JAXB3 too |
Minor addendum: As for today |
Just one comment to be not forgotten when upgrading to JAXB 3.x: addIfExistsToEpisodeSchemaBindings.xslt should be also modified, as it currently does not seem to support JAXB 3 with https://jakarta.ee/xml/ns/jaxb namespace bindings. |
The issue appears to be fixed on the main trunk but not yet released in qa build. maven-jaxb2-plugin is running an XSLT transform on the episode file after the XJC generation. Here is the (fixed) stylesheet used in the XSLT transformation: https://github.com/phax/maven-jaxb2-plugin/blob/master/plugin-core/src/main/resources/org/jvnet/jaxb2/maven2/addIfExistsToEpisodeSchemaBindings.xslt You can workaround the problem by invoke the stylesheet transformation from your POM
|
Made a pull request for supporting jaxb3 / jaxb4 #255 |
Hi,
I love this plugin and have been using it for many years. With the release of JAXB 3.0.0, I'm interested whether there are any plans to support it. I'm willing to support the development and have already toyed around some in my fork.
As a start, I have tried to gather the relevant changes below.
Please let me know if I can support this project in any way, e.g., by saying something about the desired way to integrate jaxb3 into this project. It seems rather hard to make the
core
andtesting
projects jaxb-version-agnostic because of the different package names and dependency coordinates.requirements towards plugin-development
expect bindings to be in a new namespace
<bindings xmlns="https://jakarta.ee/xml/ns/jaxb" version="3.0">...</bindings>
relevant for
RawXJC2Mojo.java
andaddIfExistsToEpisodeSchemaBindings.xslt
packages
use
jakarta.xml.bind.annotation
instead ofjavax.xml.bind.annotation
use
org.glassfish.jaxb.core.v2.schemagen.episode
instead ofcom.sun.xml.bind.v2.schemagen.episode
libraries
use
jakarta.xml.bind:jakarta.xml.bind-api
instead ofjavax.xml.bind:jaxb-api
update all
org.glassfish.jaxb
artifacts to version3.0.0
requirements towards plugin users
binding files need to be updated to the new namespace "https://jakarta.ee/xml/ns/jaxb" and have their version set to "3.0"
<bindings xmlns="https://jakarta.ee/xml/ns/jaxb" version="3.0">...</bindings>
as far as I can tell, the xjc subnamespace hasn't changed
use an updated jaxb runtime, e.g.
The text was updated successfully, but these errors were encountered: