Skip to content
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

FindBugs gives an error and creates an empty HTML report #25

Closed
Inventitech opened this issue Apr 18, 2014 · 3 comments · Fixed by #27
Closed

FindBugs gives an error and creates an empty HTML report #25

Inventitech opened this issue Apr 18, 2014 · 3 comments · Fixed by #27

Comments

@Inventitech
Copy link
Contributor

Does anybody else get the same problem when executing mvn site?

[INFO] Generating "Checkstyle" report --- maven-checkstyle-plugin:2.12
[INFO]
[INFO] Generating "FindBugs Report" report --- findbugs-maven-plugin:2.3.2
[INFO] canGenerate is true
[INFO] canGenerate is true
[INFO] Locale is en
[INFO] ****** FindBugsMojo executeReport *******
[INFO] XML outputFile is /home/mbeller/Preaching/jpacman-framework/target/findbugsXml.xml
[INFO] XML output Directory is /home/mbeller/Preaching/jpacman-framework/target
[INFO] ****** FindBugsMojo executeFindbugs *******
[INFO] Temp File is /home/mbeller/Preaching/jpacman-framework/target/findbugsTemp.xml
[INFO] Fork Value is true
[java] Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 35328
[java] at org.objectweb.asm.ClassReader.accept(Unknown Source)
[java] at edu.umd.cs.findbugs.asm.FBClassReader.accept(FBClassReader.java:44)
[java] at org.objectweb.asm.ClassReader.accept(Unknown Source)
[java] at edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:93)
[java] at edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:414)
[java] at edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:65)
[java] at edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:39)
[java] at edu.umd.cs.findbugs.classfile.impl.AnalysisCache.getClassAnalysis(AnalysisCache.java:214)
[java] at edu.umd.cs.findbugs.ba.XFactory.getXClass(XFactory.java:581)
[java] at edu.umd.cs.findbugs.ba.AnalysisCacheToAnalysisContextAdapter.setAppClassList(AnalysisCacheToAnalysisContextAdapter.java:319)
[java] at edu.umd.cs.findbugs.FindBugs2.createAnalysisContext(FindBugs2.java:785)
[java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:187)
[java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:348)
[java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1057)
[java] Java Result: 1
[INFO] No bugs found
[INFO] Generating "Surefire Report" report --- maven-surefire-report-plugin:2.17

@avandeursen
Copy link
Member

Yes, I have the same problem, and I don't see an easy solution on the web.

I propose to drop the findbugs dependency from the pom.xml -- and also do this for the jpacman-template project. (findbugs is nice to have if it works, but not a must have, and in this case it causes confusion).

@michaeldejong
Copy link
Contributor

It works fine on my machines. Using maven 3.0.5 (I know) and 3.1.1. An alternative might be the Findbugs plugin for Eclipse.

@avandeursen
Copy link
Member

It might be related to the JDK version. I'm running Java 8, and get this problem.

https://stackoverflow.com/questions/17259201/findbugs-in-eclipse-arrayindexoutofbounds-exception-when-running

Thus switching to Eclipse won't help either. My suggestion remains to drop findbugs for now.

avandeursen added a commit to SERG-Delft/jpacman-template that referenced this issue Apr 19, 2014
avandeursen added a commit that referenced this issue Apr 19, 2014
Inventitech added a commit to Inventitech/jpacman-framework that referenced this issue Aug 16, 2014
New Maven Findbugs plugin is compatible with Java 8.

(Refs SERG-Delft#25)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants