-
Notifications
You must be signed in to change notification settings - Fork 183
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
Java 9 support #105
Comments
The following points may become issues:
|
I have patch for reading classes from jimages, this is not a problem. |
(Also posted to the findbugs-discuss list) No objections to a private snapshot being used, but speaking as the maintainer of the Fedora FindBugs packages, I would very much appreciate it if you could:
These two mean that Fedora can (continue to) rebuild BCEL for FindBugs from source. |
The asm 6.0 snapshot was built from SVN 1818 version, from ASM_6_FEATURE branch.
The right approach would be something like #75.
The first draft with Java 9 support is committed to java9 branch.
|
OK, just found out that in BCEL HEAD all classes moved to new package structure (because it makes fun and of course because _maven_ needs it, see https://issues.apache.org/jira/browse/BCEL-222). If I ever needed any argument why maven is evil... Anyway. I'm playing with the idea to create a git repository fork from they SVN repo (https://commons.apache.org/proper/commons-bcel/source-repository.html) and move all classes back in git. With this git repo it should be easy to track the changes in BCEL HEAD. |
FB follows now the new JDK version scheme described in http://openjdk.java.net/jeps/223. Java versions before Java 9 will have 1 as major segment, and some meaningful number as major segment starting with Java 9. This should work for most cases.
FindBugs on Java 9 must work now, major work is done. Closing as fixed, new issues with Java 9 should be tracked by new tickets. |
Thanks! I see there are 3 branches for Java 9 development, from which one should we build a snapshot to test it in our application? |
The sources are on the https://github.com/findbugsproject/findbugs/tree/java9_bcel6_old branch, see also the announcement https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2016-June/004286.html. |
ok thanks! Congratulations for this release :) |
I have tested the new release on our project with JDK7, JDK8 and JDK9b121. It works perfectly with JDK8 and JDK9. However, the binaries have been compiled with JDK8, so we can't use it anymore with JDK7, is it intentional? |
Yes. That's the prise for Java 9. We theoretically can run on Java 7 if we would use extra jrt-fs library recompiled on 7 (there was one on github) but we practically have no one who would have time to contribute it. I do not have time to support dead systems too. |
@iloveeclipse Do you have an ETA on when version 3.1.0 might be available on Maven Central as final version? I saw that there's a SNAPSHOT version available right now. |
|
@iloveeclipse Is FindBugs still going to provide a Java 9-compatible version? I see that this issue has been closed. |
The development is moved to https://github.com/spotbugs/spotbugs. |
@iloveeclipse Thanks for the pointer. Is it correct to assume that FindBugs will never support Java 9 then? Instead users are supposed to use Spotbugs. Is that correct? |
Never say never :-) And yes, we are trying all we can do to minimize the pain for existing FindBugs users while transition to SpotBugs. I can say for myself that I'm running latest snapshot without any problems both as command line and Eclipse plugin, both on Java 8. Java 9 changed so much in so many ways during the betas that I'm pretty sure it will not work out of the box with SpotBugs anymore. At some time I've given up to download and test them because it is really time consuming, but if you would take time for testing and report the issues, we will try to fix them. |
@iloveeclipse Thanks, this information helps a lot. |
Actually just tried the latest beta, SpotBugs works running on Java 9 with |
Actually we're still using findbugs 3.1.0_preview2 with jdk9 on a weekly basis (for each new EA build) and it works fine! I'm pretty confident about Spotbugs' Java 9 support 👍 |
Yep, we know it, see spotbugs/spotbugs#268 |
Compilation error fixes: - Avoid ambiguity error when appending to Properties in Scala code (scala/bug#10418) - Use position() and limit() to fix ambiguity issue ( scala/bug#10418 (comment)) - Disable findBugs if Java 9 is used ( findbugsproject/findbugs#105) Compilation warning fixes: - Avoid deprecated Class.newInstance in Utils.newInstance - Silence a few Java 9 deprecation warnings - var -> val and unused fixes Runtime error fixes: - Introduce Base64 class that works in Java 7 and Java 9 Also: - Set --release option if building with Java 9 Note that tests involving EasyMock (easymock/easymock#193) or PowerMock (powermock/powermock#783) will fail as neither supports Java 9 currently. Author: Ismael Juma <[email protected]> Reviewers: Jason Gustafson <[email protected]> Closes #3647 from ijuma/kafka-4501-support-java-9
For more information see findbugsproject/findbugs#105. It's recommended to use SpotBugs now.
The asm 6.0 snapshot was built from SVN 1818 version, from ASM_6_FEATURE branch.
…indbugsproject#105 The support is not complete, currently packages which exist in multiple modules aren't properly supported (java.awt is an example).
The right approach would be something like findbugsproject#75.
…oject#75 FB follows now the new JDK version scheme described in http://openjdk.java.net/jeps/223. Java versions before Java 9 will have 1 as major segment, and some meaningful number as major segment starting with Java 9. This should work for most cases.
The text was updated successfully, but these errors were encountered: