-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid error message logged during execution #429
Comments
Holding off on releasing v4.0.0 until we look at this one. We might need a new v3.x as well |
@mattrpav PR provided for master |
@mattrpav just released v4 and available : https://central.sonatype.com/artifact/org.jvnet.jaxb/jaxb-maven-plugin/4.0.0 If you are not stuck with jaxb 3 api or jdk8 support, could you give it a try ? V3.0.2 with backported fix will be available in a few days. Thanks |
Yep trialed the 4.0.0 version this morning and working perfectly. Thanks for such a fast turn-around |
Many thanks to you for reporting this to us. |
Do you still plan to release 3.0.2? |
Yes but we need to work on multi release pipeline |
Unfortunately, yes... but I have to admit that this is certainly quite unusual. |
Yes and jaxb3 is not quite supported too. |
JAXB 4 requires JDK 11. |
@OLibutzki : 3.0.2 has been released (sorry for the delay 😄), enjoy ! |
Thanks, I've been waiting every day. 😉 |
The latest 3.0.1 version of the jaxb-maven-plugin logs an invalid/incorrect error message to the console during execution. Specifically I see the message
[ERROR] Could not find JAXB 2.x API classes. Make sure JAXB 2.x API is on the classpath.
It looks like maven-plugin/plugin-core/src/main/java/org/jvnet/jaxb/maven/AbstractXJCMojo.java code still contains some string versions of the old javax.xml.bind packages which the code uses in an attempt to instantiate the classes. The strings are used in the logApiConfiguration() function of the AbstractXJCMojo class.
The constants I think still needing updating:
The logApiConfiguration function may need some rework as well since it's attempting to resolve the JAXB version for logging purposes.
The text was updated successfully, but these errors were encountered: