-
Notifications
You must be signed in to change notification settings - Fork 2
What repo should we follow? #13
Comments
Well, the history is simple:
It's confusing, I agree. Edit: changed "highsource" to "elaboratebytes" in the third bullet point |
Thank you for the answer, this will certainly help others. Jaxb and the like are a tangled mess in general. We will continue using your version as its better future proofed. |
Hi @phax what fix did you need on highsource plugin ? |
Hi @laurentschoelens, with "we" you mean you are now part of the highsource committers? hth, Philip |
I'm not (still) direct committer to highsource repositories (in comparison to mattprav) but I'm in direct contact with him and provide many PR to make the project go ahead with issues and migration. For example, I'm trying to work on highsource#244 which is a very old issue but I've tried to fix with a simple change on catalog resolution handling. |
Hi @phax |
Excellent, thank you |
Hi @phax PR provided to highsource repo but with modification in code since it may fails if you get files like Regards |
Okay thanks. What are your plans on Jakarta 3 + 4 integration? Will you add it as well? |
Yes. We're consolidating all jaxb-related repos in jaxb-tools main repository. |
@phax : in fact I finally find out why you had your issue. codehaus-plexus/plexus-utils#70 :
The plexus-utils DirectoryScanner utils does not guarantee any order in returned files. You can see the PR that shall be included in 2.0.4 release : highsource#287 |
Hi @phax , We did cut off v2.0.4 of jaxb maven plugin which fixes your issue. Could you test 2.0.4 if you can and confirm issue is fixed ? Thanks |
Hi @laurentschoelens, |
Hi @phax |
Thanks, I really do need V4 for full compliance - I'll wait it up :) Besides that, I am on vacation anyway for this month and will check back in November. Thanks for your efforts so far @laurentschoelens |
Yep that was I've seen in another issue |
@phax v4 as been released ;-) |
Whoop whoop - I will have a look at it, when there is bad weather :) |
Hi @phax |
@laurentschoelens Nope - still on vacation (lucky me). Will be back on Thursday, packed with meeting untils the end of the week, so don't expect some insights before Nov 6th |
@phax : hope everything is fine since your vacations ended. |
Hi @phax |
Please follow https:/highsource/jaxb-tools- it works for all my JAXB 4 requirements as a drop-in replacement |
I think https:/evolvedbinary/jvnet-jaxb-maven-plugin should be flagged archived with notes to use this repo. Issues not open over there so hoping with your recent integration you could reach author to do that.
Now, then the upstream is problematic. Its moved again without any regard for far more support here. Maybe they just don't know. Opening similar issue there. For now this seems the most feature complete because it supports JakartaEE. The upstream still does not. Even mavens mojohaus variation supports jakartaEE. So I think this needs ironed out as its a bit confusing to users IMHO.
The text was updated successfully, but these errors were encountered: