Lines Matching full:command
111 <prompt>$ </prompt><command>gunzip -c findbugs-2.0.3.tar.gz | tar xvf -</command>
118 <prompt>C:\Software></prompt><command>unzip findbugs-2.0.3.zip</command>
218 a working directory. A typical command to do this is:
221 <prompt>$ </prompt><command>unzip findbugs-2.0.3-source.zip</command>
288 of running the command
290 <prompt>$ </prompt><command>ant <replaceable>target</replaceable></command>
295 <term><command>build</command></term>
304 <term><command>docs</command></term>
314 <term><command>runjunit</command></term>
325 <term><command>bindist</command></term>
338 After running an &Ant; command, you should see output similar to
355 building the <command>build</command> target, the working directory
376 command line user interface. This chapter describes
402 script, or run the command <screen>
403 <command>java -jar &FBHome;/lib/findbugs.jar</command></screen>
428 <filename>&FBHome;/lib/findbugs.jar</filename> using the <command>-jar</command>
429 command line switch of the JVM (<command>java</command>) executable.
437 <command>java <replaceable>[JVM arguments]</replaceable> -jar &FBHome;/lib/findbugs.jar <replaceable>options...</replaceable></command>
446 the GUI. From a command line, the command
457 The first command line option chooses the &FindBugs; user interface to execute.
463 <command>-gui</command>: runs the graphical user interface (GUI)
469 <command>-textui</command>: runs the command line user interface
475 <command>-version</command>: displays the &FindBugs; version number
481 <command>-help</command>: displays help information for the
482 &FindBugs; command line user interface
488 <command>-gui1</command>: executes the original (obsolete)
506 <term><command>-Xmx<replaceable>NN</replaceable>m</command></term>
518 <term><command>-D<replaceable>name</replaceable>=<replaceable>value</replaceable></command></term>
522 argument <command>-Duser.language=ja</command> to display
550 On Unix-like systems, use the following command to invoke the wrapper script:
552 <prompt>$ </prompt><command>&FBHome;/bin/findbugs <replaceable>options...</replaceable></command>
557 On Windows systems, the command to invoke the wrapper script is
559 <prompt>C:\My Directory></prompt><command>&FBHomeWin;\bin\findbugs.bat <replaceable>options...</replaceable></command>
566 FindBugs using the <command>findbugs</command> command.
570 <title>Wrapper script command line options</title>
571 <para>The &FindBugs; wrapper scripts support the following command-line options.
572 Note that these command line options are <emphasis>not</emphasis> handled by
578 <term><command>-jvmArgs <replaceable>args</replaceable></command></term>
584 <prompt>$ </prompt><command>findbugs -textui -jvmArgs "-Duser.language=ja" <replaceable>myApp.jar</replaceable></command>
591 <term><command>-javahome <replaceable>directory</replaceable></command></term>
601 <term><command>-maxHeap <replaceable>size</replaceable></command></term>
611 <term><command>-debug</command></term>
621 <term><command>-property</command> <replaceable>name=value</replaceable></term>
642 <title>Command-line Options</title>
650 <prompt>$ </prompt><command>findbugs <replaceable>[standard options]</replaceable> <replaceable>[GUI options]</replaceable></command>
653 The second invokes the Command Line Interface (Text UI):
656 <prompt>$ </prompt><command>findbugs -textui <replaceable>[standard options]</replaceable> <replaceable>[Text UI options]</replaceable></command>
662 This section describes the command line options supported by &FindBugs;.
663 These command line options may be used when invoking &FindBugs; directly,
668 <title>Common command-line options</title>
671 These options may be used with both the GUI and command-line interfaces.
677 <term><command>-effort:min</command></term>
690 <term><command>-effort:max</command></term>
700 <term><command>-project</command> <replaceable>project</replaceable></term>
712 <term><command></command></term>
733 <term><command>-look:</command><replaceable>plastic|gtk|native</replaceable></term>
754 <term><command>-sortByClass</command></term>
763 <term><command >-include</command> <replaceable>filterFile.xml</replaceable></term>
773 <term><command >-exclude</command> <replaceable>filterFile.xml</replaceable></term>
783 <term><command>-onlyAnalyze</command> <replaceable>com.foobar.MyClass,com.foobar.mypkg.*</replaceable></term>
805 <term><command>-low</command></term>
814 <term><command>-medium</command></term>
823 <term><command>-high</command></term>
832 <term><command>-relaxed</command></term>
842 <term><command>-xml</command></term>
847 option as <command>-xml:withMessages</command>; when this variant
856 <term><command>-html</command></term>
863 <command>-html:plain.xsl</command>, <command>-html:fancy.xsl</command> and <command>-html:fancy-hist.xsl</command>.
867 visual presentation. The <command>fancy-hist.xsl</command> an evolution of <command>fancy.xsl</command> stylesheet.
874 <command>-html:<replaceable>myStylesheet.xsl</replaceable></command>,
882 <term><command>-emacs</command></term>
891 <term><command>-xdocs</command></term>
900 <term><command>-output</command> <replaceable>filename</replaceable></term>
909 <term><command>-outputFile</command> <replaceable>filename</replaceable></term>
912 This argument is deprecated. Use <command>-output</command> instead.
918 <term><command>-nested</command><replaceable>[:true|false]</replaceable></term>
924 To disable it, add <command>-nested:false</command> to the command line
931 <term><command>-auxclasspath</command> <replaceable>classpath</replaceable></term>
942 <term><command>-userPrefs</command> <replaceable>edu.umd.cs.findbugs.core.prefs</replaceable></term>
948 This rationale behind this option is to reuse FindBugs Eclipse project settings for command
956 <term><command></command> <replaceable></replaceable></term>
982 After you have started &FindBugs; using the <command>findbugs</command> command,
1089 <title>Using the &FindBugs;™ Command Line Interface</title>
1092 The &FindBugs; Command Line Interface (or Text UI) can be used to
1101 Command Line Interface.
1200 Here is an example of invoking &Ant; from the command line, using the <literal>findbugs</literal>
1204 <prompt>[daveho@noir]$</prompt> <command>ant findbugs</command>
1536 This rationale behind this option is to reuse FindBugs Eclipse project settings for command
1809 Filters are currently only supported by the Command Line interface.
1832 <prompt>$ </prompt><command>findbugs -textui -exclude <replaceable>myExcludeFilter.xml</replaceable> <replaceable>myApp.jar</replaceable></command>
1839 <prompt>$ </prompt><command>findbugs -textui -include <replaceable>myIncludeFilter.xml</replaceable> <replaceable>myApp.jar</replaceable></command>
1860 warnings by looking at the output produced by the <command>-xml</command>
2347 The analysis options are set using the <command>-property</command>
2348 command line option. For example:
2350 <prompt>$ </prompt><command>findbugs -textui -property "cfg.noprune=true" <replaceable>myApp.jar</replaceable></command>
2462 <term><command>edu.umd.cs.findbugs.annotations.CheckForNull</command></term>
2464 <command>[Target]</command> Field, Method, Parameter
2475 <term><command>edu.umd.cs.findbugs.annotations.CheckReturnValue</command></term>
2477 <command>[Target]</command> Method, Constructor
2482 <term><command>[Parameter]</command></term>
2485 <command>priority:</command>The priority of the warning (HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
2490 <command>explanation:</command>A textual explaination of why the return value should be checked. Default value:"".
2504 <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotation</command></term>
2506 <command>[Target]</command> Type, Package
2511 command>[Parameter]</command></term>
2514 <command>value:</command>Annotation class objects. More than one class can be specified.
2519 <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
2537 <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForFields</command></term>
2539 <command>[Target]</command> Type, Package
2544 <term><command>[Parameter]</command></term>
2547 <command>value:</command>Annotation class objects. More than one class can be specified.
2552 <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
2566 <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForMethods</command></term>
2568 <command>[Target]</command> Type, Package
2573 <term><command>[Parameter]</command></term>
2576 <command>value:</command>Annotation class objects. More than one class can be specified.
2581 <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
2595 <term><command>edu.umd.cs.findbugs.annotations.DefaultAnnotationForParameters</command></term>
2597 <command>[Target]</command> Type, Package
2602 <term><command>[Parameter]</command></term>
2605 <command>value:</command>Annotation class objects. More than one class can be specified.
2610 <command>priority:</command>Default priority(HIGH, MEDIUM, LOW, IGNORE). Default value:MEDIUM.
2624 <term><command>edu.umd.cs.findbugs.annotations.NonNull</command></term>
2626 <command>[Target]</command> Field, Method, Parameter
2637 <term><command>edu.umd.cs.findbugs.annotations.Nullable</command></term>
2639 <command>[Target]</command> Field, Method, Parameter
2656 <term><command>edu.umd.cs.findbugs.annotations.OverrideMustInvoke</command></term>
2658 <command>[Target]</command> Method
2663 <term><command>[Parameter]</command></term>
2666 <command>value:</command>Specify when the super invocation should be
2685 <term><command>edu.umd.cs.findbugs.annotations.PossiblyNull</command></term>
2694 <term><command>edu.umd.cs.findbugs.annotations.SuppressWarnings</command></term>
2696 <command>[Target]</command> Type, Field, Method, Parameter, Constructor, Package
2701 <term><command>[Parameter]</command></term>
2704 <command>value:</command>The name of the warning. More than one name can be specified.
2709 <command>justification:</command>Reason why the warning should be ignored. Default value:"".
2729 <term><command>edu.umd.cs.findbugs.annotations.UnknownNullness</command></term>
2731 <command>[Target]</command> Field, Method, Parameter
2741 <term><command>edu.umd.cs.findbugs.annotations.UnknownNullness</command></term>
2743 <command>[Target]</command> Field, Method, Parameter
2779 over many directories, you may wish to use the <command>rejarForAnalysis
2780 </command> script to make
2783 analysis. This can be particularly useful in combination with the 'find' command
2784 on unix systems; e.g. <command>find . -name '*.jar' | xargs rejarForAnalysis
2785 </command>.
2789 The <command>rejarForAnalysis</command> script
2793 Instead of running FindBugs on the entire project, you may use <command>
2794 rejarForAnalysis</command> build one large, all-inclusive jarfile
2795 containing all classes, invoke <command>rejarForAnalysis</command>
2798 the <command>-auxclasspath</command>.
2802 These are the options accepted by the <command>rejarForAnalysis</command> script:
2807 <term><command>-maxAge</command> <replaceable>days</replaceable></term>
2815 <term><command>-inputFileList</command> <replaceable>filename</replaceable></term>
2823 <term><command>-maxClasses</command> <replaceable>num</replaceable></term>
2831 <term><command>-prefix</command> <replaceable>class name prefix</replaceable></term>
2869 <command>setBugDatabaseInfo</command> (<xref linkend="setBugDatabaseInfo" />) command.
2876 each version. The <command>filterBugs</command> command allows you to refer
2907 All tools for FindBugs data mining are can be invoked from the command line,
2912 Briefly, the command-line tools are:</para>
2916 <term><command><link linkend="unionBugs">unionBugs</link></command></term>
2925 <term><command><link linkend="computeBugHistory">computeBugHistory</link></command></term>
2936 <term><command><link linkend="setBugDatabaseInfo">setBugDatabaseInfo</link></command></term>
2943 <term><command><link linkend="listBugDatabaseInfo">listBugDatabaseInfo</link></command></term>
2950 <term><command><link linkend="filterBugs">filterBugs</link></command></term>
2956 <term><commandcommand></term>
2963 <term><command><link linkend="defectDensity">defectDensity</link></command></term>
2971 <term><command><link linkend="convertXmlToText">convertXmlToText</link></command></term>
2985 you can use this command to combine the separately generated xml bug warning files into
2988 <para>Do <emphasis>not</emphasis> use this command to combine results from analyzing different versions of the same
2989 file; use <command>computeBugHistory</command> instead.</para>
2991 <para>Specify the xml files on the command line. The result is sent to standard output.</para>
2997 <para>Use this command to generate a bug database containing information from different builds or versions
3006 First create a taskdef for <command>computeBugHistory</command> in your
3033 <title>Options for computeBugHistory command</title>
3037 <entry>Command-line option</entry>
3057 <para>This command is used to select a subset of warnings from a FindBugs XML warning file
3060 This command takes a sequence of options, and either zero, one or two
3061 filenames of findbugs xml bug files on the command line.</para>
3062 <para>If no file names are provided, the command reads from standard input
3069 First create a taskdef for <command>filterBugs</command> in your
3095 <title>Options for filterBugs command</title>
3099 <entry>Command-line option</entry>
3139 <para>This command generates a table containing counts of the numbers of warnings
3144 First create a taskdef for <command>mineBugHistory</command> in your
3171 <title>Options for mineBugHistory command</title>
3175 <entry>Command-line option</entry>
3231 This command lists information about defect density (warnings per 1000 NCSS) for the entire project and each class and package.
3232 It can either be invoked with no files specified on the command line (in which case it reads from standard input)
3233 or with one file specified on the command line.</para>
3261 This command converts a warning collection in XML format to a text
3266 First create a taskdef for <command>convertXmlToText</command> in your
3281 <title>Options for convertXmlToText command</title>
3285 <entry>Command-line option</entry>
3294 <row><entry></entry> <entry>format="text"</entry> <entry>generate plain text output with one bug per line (command-line default)</entry></row>
3315 This command sets meta-information in a specified warning collection.
3320 First create a taskdef for <command>setBugDatabaseInfo</command> in your
3351 <entry>Command-line option</entry>
3374 <para>This command takes a list of zero or more xml bug database filenames on the command line.
3425 <para>You can use the command:</para>
3480 We could also generate that information directly, without creating an intermediate db.xml file, using the command
3502 Given the db.xml file that contains the results for all the jdk1.6.0 builds, the following command will show the history of high and medium priority correctness warnings:
3833 stylesheets, and made improvements to the <command>-xml:withMessages</command>
