-
Notifications
You must be signed in to change notification settings - Fork 582
static import only from classes and interfaces #293
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
Comments
The bug is reported for JDK 7 and fixed in JDK 8b43, and this library's 5.0 release will require JDK 8. We will switch to wildcard static imports but if Fedora 26 uses a JDK 8 version affected, it sounds like the package could use some updating? |
I use java-1.8.0-openjdk-devel-1:1.8.0.131-7.b12.fc26 |
@rapgro please give the tip of |
Do you mean to build from latest commits of the 4.1.x-stable branch? I assumed to build successfully from official tarball releases, so could you provide a 4.1.2 with the patch for static imports applied? |
@rapgro there are no tarball releases of this client, as of 4.0 it is only released to Maven repositories. If you are referring to GitHub source tarballs, they are produced automatically for GitHub for any tag that's pushed. While we can push a tag it should be no different from producing a tarball from your local repository on the right branch. |
Since the files that use static imports all seem to be in tests (which makes sense, given that we are importing functions from Hamcrest and Mockito), another option should be using |
Well, running the tests is nice after built for RPM. |
@rapgro I have pushed a tag that points to daa6300. GitHub will produce a source tarball from it. |
Uh oh!
There was an error while loading. Please reload this page.
These errors occur for rabbitmq-java-client version 4.1.1 with openjdk 1.8 on Fedora 26. It's a compiler bug, possible workaround is given on stackoverflow.
https://stackoverflow.com/questions/11782076/static-import-only-from-classes-and-interfaces
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7159016
The text was updated successfully, but these errors were encountered: