JAXB plugin v3.x roadmap

Question

JAXB plugin v3.x roadmap

mattrpav opened this issue 2 years ago · 36 comments

mattrpav commented 2 years ago

Current plans for v3.x roadmap:

Features

Release a jakarta compatible v3.x release
Migrate to new groupId/artifactId org.jvnet.jaxb/jaxb-maven-plugin (more recent maven standard)
Align plugin version with jaxb release version as much as possible
Migrate jaxb plugin-plugin projects (and maybe jaxb2-basics) to be child modules of this tree
Add toolchain awareness

Deprecation

JDK 1.6 and 1.7 support
Dropping plugin-2.0, 2.1 and 2.2 support.

The goal of this is to make it more straight forward to consume the modules (esp plugin-plugins) and know if versions are compatible in light of the major JEE/Jakarta changes. Support for multiple versions aligning to various jaxb versions (too complicated and confusing to users in light of jakarta change)

Please use this ticket for comments, discussion and questions.

Thanks!

mattrpav commented a year ago

#389

🎉1

Answer 1 · 2022-06-29T07:59:22.000Z

Any progress on this?

Answer 2 · 2022-09-01T21:17:17.000Z

The new jakarta packages (JAXB 3 and 4) work with the evolvedbinary fork:

<plugin>
    <groupId>com.evolvedbinary.maven.jvnet</groupId>
    <artifactId>jaxb30-maven-plugin</artifactId>
    <version>0.15.0</version>
</plugin>

There's no point continuing to support the old javax stuff any more. There's already plenty of historic releases that support that. There simply needs to be a maven-jaxb-plugin that works with the newer packages with JDK 11 and above. (note that Jakarta XML Binding 4 requires Java 11 or higher)

Answer 3 · 2023-01-11T14:50:29.000Z

Hello,

Are there any plans to adopt jaxb30-maven-plugin fork for the main project? I checked the fork, it seems to be working, but I do not want to include it to the project without maintenance.

Maybe have it as a separate branch with Jakarta support? Preferably the support of JDK 8 should not be dropped, as Jakarta 3 supports Java 8.

Best regards,
Aleksandr.

Answer 4 · 2023-01-11T15:15:44.000Z

Yes, jakarta support is coming

Answer 5 · 2023-01-27T21:19:36.000Z

The new jakarta packages (JAXB 3 and 4) work with the evolvedbinary fork:

Can you provide the dependencies you used in both the pom dependencies section and in the jaxb30-maven-plugin section to make it work?

When I provide jaxb 3.x dependencies, the build complains of missing class like javax/xml/bind/JAXBException

Answer 6 · 2023-01-28T09:01:43.000Z

Can you provide the dependencies you used in both the pom dependencies section and in the jaxb30-maven-plugin section to make it work?

https://github.com/SingingBush/jaxb-example/blob/main/pom.xml

Answer 7 · 2023-02-22T15:05:33.000Z

Just wondering if this is something which is going to be merged to main or you guys are working on the jakarta support in another place @mattrpav?

UPDATE: forgot to add the link to the PR which i was wondering about #255

Also wondering if there are any thoughts on this project here https://github.com/patrodyne/hisrc-higherjaxb or any plans to integrate changes back to the original project?

Answer 8 · 2023-03-17T22:10:04.000Z

@mattrpav any news on this ?

Answer 9 · 2023-03-29T08:23:30.000Z

Hello,

SpringBoot stops OSS support of version 2.7.x at the end of the year. The newer version SpringBoot 3.x comes with Jakarta 4, thus requiring all applications to upgrade to Jakarta namespaces, and the upgrade becomes vital for a lot of users.

Could you please provide with a rough estimate on the planning of when the Jakarta support becomes available?

Thank you!

Best regards,
Aleksandr.

Answer 10 · 2023-03-29T08:51:39.000Z

Hi @bsanchezb

There's a PR #255 for this upgrade but we are waiting for @mattrpav to check and merge it (and then release it).
We've tested the updated plugin on many projects (manual build) and it's OK.

The https://github.com/highsource/jaxb2-basics plugin also have same PR for jakarta migration namespace

Regards

Answer 11 · 2023-07-12T13:14:04.000Z

I know that probably that's not an appropriate place to share it, but I came up with the simplest workaround that got me through the javax -> jakarta problem during working on my project:

Simply add ant replace after the jaxb plugin:

<build>
        <plugins>
            <plugin>
                <groupId>org.jvnet.jaxb</groupId>
                <artifactId>jaxb-maven-plugin</artifactId>
                <!-- your configuration of the plugin -->
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-antrun-plugin</artifactId>
                <executions>
                    <execution>
                        <phase>generate-sources</phase>
                        <configuration>
                            <target>
                                <replace dir="target/generated-sources" value="jakarta.xml.bind">
                                    <include name="**/*.java"/>
                                    <replacetoken>javax.xml.bind</replacetoken>
                                </replace>
                            </target>
                        </configuration>
                        <goals>
                            <goal>run</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
...

It is hacky but I need to get job done :-)

Answer 12 · 2023-07-12T13:58:14.000Z

@mikhail-putilov thanks for sharing this tip.
The big part before migrating to jakarta is currently under review by @mattrpav
After that we'll be able to provide a version compatible with jakarta

Answer 13 · 2023-08-09T08:40:26.000Z

Any concrete schedule around that? There is no Spring Boot 2.X support by the end of the year so time is running out....

Answer 14 · 2023-08-09T08:48:32.000Z

Any concrete schedule around that? There is no Spring Boot 2.X support by the end of the year so time is running out....

Hi @titro

I'll not give you hope of a concrete date since we're still working on bugfixes on the v2 version (which support jaxb 2.3).

But what I can say is that we're doing active work on this and hope to cut 2.0.4 release this week. Then work on jakarta version based on initial PR I provided so we should be able to cut 3.0.0 release very soon.
In the meantime, you should be able to use this workaround #233 (comment)

Feel free to come back if you have any problems with it.

Answer 15 · 2023-08-20T21:12:22.000Z

Jakarta is coming, the major refactoring is going to land this week and jaxb3 support should come shortly after.
Stay tuned

Answer 16 · 2023-08-27T14:40:33.000Z

Excellent, thank you for the update!

I'll be happy to migrate w3c-schemas and ogc-schemas to Jakarta as soon as your work lands.

Answer 17 · 2023-08-27T18:03:52.000Z

Excellent, thank you for the update!

I'll be happy to migrate w3c-schemas and ogc-schemas to Jakarta as soon as your work lands.

Annox and jaxb-annotate-plugin are now part of jaxb-tools
Hyperjaxb is on it's way too

Answer 18 · 2023-08-27T19:17:06.000Z

Have you decided whether/if it's possible to keep the existing groupId/domain?

Answer 19 · 2023-08-27T19:21:00.000Z

Have you decided whether/if it's possible to keep the existing groupId/domain?

Didnt understand your point...
All artifacts are now published under org.jvnet.jaxb

Answer 20 · 2023-08-27T19:44:50.000Z

@soc could you reword / precise your question please ? 😃

Answer 21 · 2023-08-27T19:45:44.000Z

I think you answered my question, thanks. :-)

Answer 22 · 2023-08-27T19:47:34.000Z

I think you answered my question, thanks. :-)

And is it good news ? 😀

Answer 23 · 2023-08-27T19:51:24.000Z

It means that from my understanding you managed to get control over the domain, and therefore are able to publish artifacts under the existing coordinates?

Answer 24 · 2023-08-27T20:02:17.000Z

It means that from my understanding you managed to get control over the domain, and therefore are able to publish artifacts under the existing coordinates?

Yes @mattrpav take over maintenance and managed to publish under the main groupId org.jvnet.jaxb (will also publish relocation poms to help migration) and I'm new collaborator to the project from few weeks now thanks to him

Answer 25 · 2023-08-30T14:02:11.000Z

FYI: I have published w3c-schemas and ogc-schemas using the hack mentioned in #233 (comment), but will do a proper patch release after JAXB supports 3.x.

Answer 26 · 2023-09-01T21:32:43.000Z

One thing I realized is that w3c-schemas, ogc-schemas and ogc-tools-gml-jts still have a hidden dependency on javax.xml.bind caused by generated code using org.jvnet.jaxb2_commons.locator.ObjectLocator which extends javax.xml.bind.ValidationEventLocator.

So hopefully there is also a new release of jaxb2_commons to address this.

Answer 27 · 2023-09-02T05:33:20.000Z

One thing I realized is that w3c-schemas, ogc-schemas and ogc-tools-gml-jts still have a hidden dependency on javax.xml.bind caused by generated code using org.jvnet.jaxb2_commons.locator.ObjectLocator which extends javax.xml.bind.ValidationEventLocator.

So hopefully there is also a new release of jaxb2_commons to address this.

@soc we hope to get a new release soon (2.0.6) and then move to jakarta version

Answer 28 · 2023-09-26T10:04:57.000Z

Any news on jaxb 3 Jakarta support for the JAXB Maven Plugin?

Answer 29 · 2023-09-26T11:49:36.000Z

Planning to release shortly! Hopefully, within the next 5-10 days.

Watch the v3 milestone to keep tabs on it

Answer 30 · 2023-09-26T12:13:36.000Z

@mattrpav thank you for the very fast response and for your work!

Answer 31 · 2023-09-29T07:28:12.000Z

Planning to release shortly! Hopefully, within the next 5-10 days.

Thank you. I think we all can't wait to get v3.

Count-Down: 7 days to go.

Answer 32 · 2023-09-29T08:26:22.000Z

We are doing one last major change on v3 with new namespace for plugins, with support of older and warning to move to newer.
Older namespace support will be dropped after v4-based plugin.
Once done, and tested, we'll be ready to GO 🚀

Answer 33 · 2023-10-03T19:53:06.000Z

Hello everyone
Version 3.0.0 released (followed by 3.0.1 bugfix)
Working on 4.0 now
Enjoy

Answer 34 · 2023-10-12T07:35:23.000Z

I tried the new plugin and it works nicely and the classes are generated. The only thing I didn't get working was the "toString" Plugin so I had to throw this out...

Answer 35 · 2023-10-12T09:06:05.000Z

@Lonzak : could you share more context on this error of the toString plugin ?
If needed, you can create a question issue so we can help you with this 😄