Bump versions, remove workaround in XjcWorker

[ghost]

Updated the jaxb-xjc to version 2.3.3. According to this commit message it should improve compatibility with Java 11+. For example JPMS module descriptors are added. It also contains the merged PR of @bjornvester which fixes the file leak issue. So I also removed the workaround in com.github.bjornvester.xjc.XjcWorker.

Note that in JAXB RI 2.3.3 the class com.sun.xml.bind.Util is renamed to com.sun.xml.bind.Utils in this commit. This can be a breaking change in some cases.

I'm writing my specific issue here so people can (hopefully) find it via search engines so they won't have to spend hours debugging 😄
In my case I generated a fresh project with https://start.spring.io/.
After adding this xjc-gradle-plugin my build broke with a vague error: ERROR: Unable to load class 'com.sun.xml.bind.Util'.
After some digging I figured that Spring's dependency management enforces the latest JAXB RI 2.3.3, which causes weird classpath issues. In this case the class com.github.bjornvester.xjc.XjcWorker makes use of com.sun.tools.xjc.Options, which in turn contains the following line:
private static final Logger logger = com.sun.xml.bind.Util.getClassLogger();.
This results in a ClassNotFoundException being thrown because thexjc-gradle-plugin uses com.sun.tools.xjc.Options from jaxb-xjc 2.3.2 (containing Util) and Spring enforced jaxb-runtime 2.3.3 (containing Utils). So double-check the exact versions on your classpath.

[ghost]

@bjornvester shameless bump

[rovangju]

Thanks for the patch - I got bit by this. Your search engine plan worked :)

[ghost]

@rovangju in case it helps, I published my fork to the Gradle plugins portal so I could use it at work (we have a corporate repository that proxies the plugins portal and our CI server uses only that repo).
See https://plugins.gradle.org/plugin/com.github.kad-leeuwg1.xjc for more details. Keep in mind that it's a fork, so I would advice to switch back to this plugin as soon as this pull request is merged.