-
Notifications
You must be signed in to change notification settings - Fork 107
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
Error running japicmp-maven-plugin:0.14.4:cmp on Java 16-EA #275
Comments
I am able to reproduce it with Java 16-EA. It happens when |
I am having the same issue in our project as well and found this already reported issue. Apart from including JAXB as a dependency, have you by any chance thought about using the |
We see this as well over in Apache Commons components, but maybe not because of JAXB, for example in Apache Commons VFS builds: https://github.com/apache/commons-vfs/ We see:
|
It is not only JAX-B that I have to change. Moving to Upgrading to version 3.6.0 of the Using the Btw: You can workaround this issue until I have released a new version by setting the following JVM option: |
…en-plugin-plugin to 3.6.0 and to maven-resolver-api (eclipse-aether)
Fixed: 0.15.1 |
Great, thanks @siom79! |
- Needed to bump minimum source/target versions for compiler (1.6 no longer supported). - Needed to bump version of japicmp which fixes siom79/japicmp#275 for JDK 16. - Needed to adjust apr path for brew dependency on Mac.
Hi, thanks for the great japicmp plugin, I have started using it in my jsoup library to validate compatibility and have found it very useful.
I have GitHub Actions running CI builds across multiple Java versions including the Java 16 Early Access build.
Here's a passing round (from 16-ea ubuntu):
https://github.com/jhy/jsoup/runs/1556442000?check_suite_focus=true
And now on a subsequent run, this error is created:
(Please see the report url - https://github.com/jhy/jsoup/runs/1556669892?check_suite_focus=true - for the full trace)
All the other Java versions (8, 9, 11, 15, on Ubuntu, Windows, Mac) are passing. All the 16-ea (Ubuntu, Windows, Mac) failed with the same error.
The Java version on both executions (full pass, and the fail on 16-ea) is listed as
Java version: 16-ea, vendor: Azul Systems, Inc., runtime: /opt/hostedtoolcache/jdk/16.0.0-ea/x64
I suspect that the specific build of 16.0.0 may have changed between runs.
I understand that this is an EA version and there will be churn and it may not be necessarry to make changes to your code -- perhaps the Java build reverts the change. I wanted to flag it for you earlier for your consideration. Pardon me if I've missed some details or have misconfigured my project. For now, as the builds continue to fail due to this issue, I am disabling testing on 16-ea.
The text was updated successfully, but these errors were encountered: