Discussion:
[Eclipse plugin] java.lang.NoClassDefFoundError: Could not initialize class edu.umd.cs.findbugs.Analyze
BoD
2014-06-07 13:22:08 UTC
Permalink
Hi!

I just installed a fresh version of Eclipse Kepler, and the Findbugs
plugin (I used the Eclipse Marketplace, so I believe it is the latest
version - in the UI it says Findbugs v2.0.3).
When running the analysis I have this error:
java.lang.NoClassDefFoundError: Could not initialize class
edu.umd.cs.findbugs.Analyze

I googled and didn't find anything :(

Any idea?

Thanks!
--
BoD
BoD
2014-06-07 22:53:15 UTC
Permalink
After looking more at the 'Errors' view of Eclipse, I believe I am
facing this bug:
http://sourceforge.net/p/findbugs/bugs/1228

Indeed I am running Eclipse on the latest JDK8.

But the bug is marked as resolved in v2.0.3!
Any idea?

Thanks!
--
BoD
Post by BoD
Hi!
I just installed a fresh version of Eclipse Kepler, and the Findbugs
plugin (I used the Eclipse Marketplace, so I believe it is the latest
version - in the UI it says Findbugs v2.0.3).
java.lang.NoClassDefFoundError: Could not initialize class
edu.umd.cs.findbugs.Analyze
I googled and didn't find anything :(
Any idea?
Thanks!
Andrey Loskutov
2014-06-08 16:22:54 UTC
Permalink
Post by BoD
After looking more at the 'Errors' view of Eclipse, I believe I am
http://sourceforge.net/p/findbugs/bugs/1228
Indeed I am running Eclipse on the latest JDK8.
But the bug is marked as resolved in v2.0.3!
Any idea?
Yes, it was a mistake to mark it fixed in 2.0.3. In fact, the bug is fixed on
both 2.0.3+ branch and 3.0.0, but the fix is not *released* yet. Simply grab
the latest daily build from the FB plugin (3.0.0) and be happy with it :-)
--
Kind regards,
google.com/+AndreyLoskutov
BoD
2014-06-09 08:01:43 UTC
Permalink
Thanks a lot for your reply.

I will try to do that :)
--
BoD
Post by Andrey Loskutov
Post by BoD
After looking more at the 'Errors' view of Eclipse, I believe I am
http://sourceforge.net/p/findbugs/bugs/1228
Indeed I am running Eclipse on the latest JDK8.
But the bug is marked as resolved in v2.0.3!
Any idea?
Yes, it was a mistake to mark it fixed in 2.0.3. In fact, the bug is fixed on
both 2.0.3+ branch and 3.0.0, but the fix is not *released* yet. Simply grab
the latest daily build from the FB plugin (3.0.0) and be happy with it :-)
Loading...