-
-
Notifications
You must be signed in to change notification settings - Fork 808
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
Defining classes in Java 10 EA build fails because it complains about Java version number #370
Comments
This is the Solr workaround: https://issues.apache.org/jira/browse/SOLR-11606 We disable all tests using an assume if Mockito/ByteBuddy does not support the current runtime. |
simon04
pushed a commit
to JOSM/josm
that referenced
this issue
Nov 4, 2017
…s automatically in this case Workaround to jqno/equalsverifier#177 / raphw/byte-buddy#370 Inspired by https://issues.apache.org/jira/browse/SOLR-11606 git-svn-id: http://josm.openstreetmap.de/svn/trunk@13079 0c6e7542-c601-0410-84e7-c038aed88b3b
floscher
pushed a commit
to floscher/josm
that referenced
this issue
Nov 5, 2017
…s automatically in this case Workaround to jqno/equalsverifier#177 / raphw/byte-buddy#370 Inspired by https://issues.apache.org/jira/browse/SOLR-11606 git-svn-id: https://josm.openstreetmap.de/svn/trunk@13079 0c6e7542-c601-0410-84e7-c038aed88b3b
sormuras
referenced
this issue
in junit-team/junit5
Nov 6, 2017
Fixed on master and made more robust for future version increments. Will be fixed with the next release. |
Bugfix is released. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using Mockito to run Mocking test under the today-released Java 10 EA build 29, it fails when tyring to define the class:
This error message looks a bit too restrictive: I'd change the check to only require a minimum Java version (like 9) and then further try to mock instead of giving up.
This prevents us from testing Apache Solr with Java 10. We need to disable all mocking tests with Java 10. When changing the check to allow "10" as alias for "9" and rebuilding bytebuddy, everything works.
From Mark Reinhold's mail about the half-yearly release, the proposed spec also tells that the class file version is increased every half year, so the current way of doing those checks is tooo restrictive. There should be at least a "fallback" so it tries to do everything with latest known Java version first before giving up.
The text was updated successfully, but these errors were encountered: