[
http://jira.codehaus.org/browse/MFINDBUGS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186220#action_186220
]
Mike Mormando edited comment on MFINDBUGS-86 at 8/6/09 1:25 PM:
----------------------------------------------------------------
I downloaded and tried using Findbugs 1.3.9-rc1, and ran it through the GUI
with no problems. It does look like it was the 2.2 snapshot, though when I was
looking at it yesterday for some reason I thought the jar said -rc1, I was
probably confusing it with the actual findbugs 1.3.9 jar.
Now, when I ran findbugs 1.3.9-rc1 through their batchfile this morning it
worked fine. Now I'm trying to launch it via mvn findbugs:gui I'm getting the
following stacktrace:
[INFO] [findbugs:gui]
Exception in thread "Thread-4" java.lang.NoSuchMethodError:
org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V
at
edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:93)
at
edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:414)
at
edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:65)
at
edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:39)
at
edu.umd.cs.findbugs.classfile.impl.AnalysisCache.getClassAnalysis(AnalysisCache.java:214)
at
edu.umd.cs.findbugs.FindBugs2.buildReferencedClassSet(FindBugs2.java:683)
at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:184)
at edu.umd.cs.findbugs.gui2.BugLoader.doAnalysis(BugLoader.java:80)
at
edu.umd.cs.findbugs.gui2.AnalyzingDialog$AnalysisThread.run(AnalyzingDialog.java:232)
Just to verify, I launched findbugs gui via the batch file on Windows, which
the only change I made was to set JAVA_HOME to jdk 6, just as I do in my maven
batch file, so I can have a "known" jdk to run against. The gui launched from
the batchfile seems to work on any project I run it on, the one launched via
mvn findbugs:gui throws the above stacktrace.
was (Author: mezmo):
I downloaded and tried using Findbugs 1.3.9-rc1, and ran it through the GUI
with no problems. It does look like it was the 2.2 snapshot, though when I was
looking at it yesterday for some reason I thought the jar said -rc1, I was
probably confusing it with the actual findbugs 1.3.9 jar.
Now, when I ran findbugs 1.3.9-rc1 through their batchfile this morning it
worked fine. Now I'm trying to launch it via mvn findbugs:gui I'm getting the
following stacktrace:
[INFO] [findbugs:gui]
Exception in thread "Thread-4" java.lang.NoSuchMethodError:
org.objectweb.asm.ClassReader.accept(Lorg/objectweb/asm/ClassVisitor;I)V
at
edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:93)
at
edu.umd.cs.findbugs.classfile.engine.ClassParserUsingASM.parse(ClassParserUsingASM.java:414)
at
edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:65)
at
edu.umd.cs.findbugs.classfile.engine.ClassInfoAnalysisEngine.analyze(ClassInfoAnalysisEngine.java:39)
at
edu.umd.cs.findbugs.classfile.impl.AnalysisCache.getClassAnalysis(AnalysisCache.java:214)
at
edu.umd.cs.findbugs.FindBugs2.buildReferencedClassSet(FindBugs2.java:683)
at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:184)
at edu.umd.cs.findbugs.gui2.BugLoader.doAnalysis(BugLoader.java:80)
at
edu.umd.cs.findbugs.gui2.AnalyzingDialog$AnalysisThread.run(AnalyzingDialog.java:232)
> Changing project sourceEncoding to UTF-8 causing SAX parse error
> ----------------------------------------------------------------
>
> Key: MFINDBUGS-86
> URL: http://jira.codehaus.org/browse/MFINDBUGS-86
> Project: Maven 2.x FindBugs Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: Windows XP JDK-1.6,and JDK 1.5 on Debian AMD-64, maven
> 2.1 and 2.2.
> Reporter: Mike Mormando
> Assignee: Garvin LeClaire
>
> This effects either the plugin version 2.2-rc1 or findbugs proper, 1.3.9rc1.
> I just set the sourceEncoding on my projects to UTF-8 in the POM properties,
> and I get a SAX error when findbugs creates its XML file. It works fine with
> plugin 2.1 and findbugs 1.3.8.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
