[VOTE] Release jaxb2-maven-plugin 3.0.0

742 views
Skip to first unread message

Dan Tran

unread,
Jan 31, 2021, 1:17:12 AM1/31/21
to mojoha...@googlegroups.com
Hello all,

I'd like to release version 3.0.0 of the jaxb2-maven-plugin.

We fixed 2 issues within the plugin since the last release:




Vote passed by lazy consensus after 48H

 [ ] +1 
 [ ] +0 
 [ ] -1 

Cheers

-D


lasse.k....@gmail.com

unread,
Jan 31, 2021, 2:24:07 AM1/31/21
to mojohaus-dev
Hi. If I am reading it right, the new version only works with JAXB 3.0.0 + (Jakarta namespaces) and old versions then with 2.x.y versions (with Javax namespaces).

Like discussed in the Github issue, renaming the artifact to not contain the number "2" would make sense, but I suppose this will do also as long as the docs are updated to address the issue at some point.

Dan Tran

unread,
Jan 31, 2021, 3:27:02 AM1/31/21
to mojoha...@googlegroups.com
Yes,  it is released under the assumption that it is backward compatible with JAXB v2.  @adamretter  please confirm

Thanks

-D

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/8ce92ef9-7d44-42a0-85cc-4262fd473ba7n%40googlegroups.com.

Anders Hammar

unread,
Jan 31, 2021, 11:21:25 AM1/31/21
to mojoha...@googlegroups.com
Doing some quick reading I vote -1 as we're now using "Jakarta XML Binding" (not "Java API for XML Binding (JAXB), version 2+") and the docs should then be updated to reflect this.

Some examples talk about compiling for Java 1.7 (and even 1.6). Will that even work now with JAXB 3? Should be updated if not.

There are links to the old JAXB 2 ref impl which should be changed to the new jaxb page [1].

Also, as a side note, I wonder if the dependencies are correct. The description for jaxb-xjc [2] says:
"Old JAXB Binding Compiler."
Sounds like there is a better way now.

I'd like to end with that I fully appreciate that there is a community request to get this released. But I also think that the PR that updated to JAXB 3 should have included updates to the docs. Changing code is "easy", but keeping the docs good and updated is often less fun but equally important. Realising with bad or even incorrect documentation will most likely cause frustration and it could also be bad stating false things (like what API we're using).


/Anders

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.

Dan Tran

unread,
Jan 31, 2021, 11:17:51 PM1/31/21
to mojoha...@googlegroups.com
base on feedback, I am going to cancel this vote.  I have the facility to release any plugin but lacking time and incentive to maintain it. What is the process to invite contributors to mojohaus?

Thanks

-D

Adam Retter

unread,
Feb 2, 2021, 9:13:33 AM2/2/21
to mojohaus-dev

Hi there everyone,

So I am the guy that submitted the PR to add support for JAXB 3 support.

Indeed, as a few have already pointed out, JAXB 3 support is not drop-in compatible with 2.x.y versions, as the package namespace has changed now that newer versions of J2EE and JAXB have been moved out of the JDK itself. I perhaps did not make that clear enough in my PR.

However, I don't think there will likely be any more 2.x.y versions of JAXB coming along. So perhaps it is safe to say that the previous versions of your excellent jaxb2-maven-plugin which were number 2.x.x were for JAXB 2, and versions numbered 3.x.x are for JAXB 3? Obviously that would need to be made clear in the docs. I also might suggest that either 1) dropping the "2" from the name, or 2) renaming to jaxb3-maven-plugin might help users understand.

Anyway, sorry if I caused any issues for you all. I really just wanted to help out get JAXB 3 support going as I could not find any plugin that supported it.

Kind regards. Adam.
Reply all
Reply to author
Forward
0 new messages