You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CC-XCJ will not work for the new "jakarta" namespaces of jaxb/activation-api.
In my fork I did a couple of changes to modernize the dependencies and also support the jakarta namespace (see Boris-de/CC-XJC#1). This is a hard cut change after which only jakarta will be possible, but given that there was no release needed for jaxb api in the last 10 years I guess it is not worth trying to create one build for both or something like that.
My change currently bumps the required java version to 11 because that was the easiest thing to do, but with a bit of effort it might be possible to still support java 8. Java 17 should work as well, it's just that the integration tests fail because of a java17 related bug in jaxb2-basics (see Boris-de/CC-XJC#8)
If you are interested in publishing a new CC-XJC version, I'd be happy to submit a PR here and adapt my changes if you have any suggestions/requirements. Otherwise I'd go ahead and publish a version at new maven coordinates for others that are still using CC-XJC.
The text was updated successfully, but these errors were encountered:
FYI: I've created a release from Boris-de/CC-XJC at de.wcht.cc-xjc:cc-xjc-plugin:3.0.0.
Still willing to adapt my changes and make a PR with the needed change here if you want to revive the project.
CC-XCJ will not work for the new "jakarta" namespaces of jaxb/activation-api.
In my fork I did a couple of changes to modernize the dependencies and also support the jakarta namespace (see Boris-de/CC-XJC#1). This is a hard cut change after which only jakarta will be possible, but given that there was no release needed for jaxb api in the last 10 years I guess it is not worth trying to create one build for both or something like that.
My change currently bumps the required java version to 11 because that was the easiest thing to do, but with a bit of effort it might be possible to still support java 8. Java 17 should work as well, it's just that the integration tests fail because of a java17 related bug in jaxb2-basics (see Boris-de/CC-XJC#8)
If you are interested in publishing a new CC-XJC version, I'd be happy to submit a PR here and adapt my changes if you have any suggestions/requirements. Otherwise I'd go ahead and publish a version at new maven coordinates for others that are still using CC-XJC.
The text was updated successfully, but these errors were encountered: