Translation options

-b <build_id>

Specifies a build ID. OpenText SAST uses a build ID to track the files that are compiled and combined as part of a build, and then later, to scan those files.

Equivalent property name:
com.fortify.sca.BuildID

Specifies a colon-separated list of languages to exclude from the translation phase. The valid language values are

abap, actionscript, apex, cfml, cobol, configuration, cpp, dart, dotnet, golang, objc, php, python, ruby, swift, and vb.

Equivalent property name:
com.fortify.sca.DISabledLanguages

Equivalent property name:
com.fortify.sca.EnabledLanguages

-exclude
<file_specifiers>

Specifies the files to exclude from the translation. Files excluded from translation are also not scanned. Separate multiple file paths with semicolons (Windows) or colons (non-Windows). The following example excludes all Java files in any Test subdirectory.

sourceanalyzer -b MyProject –cp "**/*.jar" "**/*" 
-exclude "**/Test/*.java"

See Specifying files and directories for more information on how to use file specifiers.

-encoding <encoding_name>

Specifies the source file encoding type. OpenText SAST enables you to scan a project that contains differently encoded source files. To work with a multi-encoded project, you must specify the -encoding option in the translation phase, when OpenText SAST first reads the source code file. OpenText SAST remembers this encoding in the build session and propagates it into the FVDL file.

Valid encoding names are from the java.nio.charset.Charset.

Typically, if you do not specify the encoding type, OpenText SAST uses file.encoding from the java.io.InputStreamReader constructor with no encoding parameter. In a few cases (for example with the ActionScript parser), OpenText SAST defaults to UTF-8 encoding.

-nc

-noextension-type <file_type>

Specifies the file type for source files that have no extension. The valid file type values are ABAP, ACTIONSCRIPT, APEX, APEX_OBJECT, APEX_TRIGGER, ARCHIVE, ASPNET, ASP, ASPX, BITCODE, BSP, BYTECODE, CFML, COBOL, CSHARP, DART, DOCKERFILE, FLIGHT, GENERIC, GO, HCL, HOCON, HTML, INI, JAVA, JAVA_PROPERTIES, JAVASCRIPT, JINJA, JSON, JSP, JSPX, JUPYTER, KOTLIN, MSIL, MXML, OBJECT, PHP, PLSQL, PYTHON, RUBY, RUBY_ERB, SCALA, SWIFT, SWC, SWF, TLD, SQL, TSQL, TYPESCRIPT, VB, VB6, VBSCRIPT, VISUAL_FORCE, VUE, and XML, and YAML .

Specifies to include build script files that have the same name as a build tool (such as gradlew) during translation as source files.

Equivalent property name:
com.fortify.sca.DisableCompilerName

Specifies the directory to store intermediate files generated in the translation and analysis phases. OpenText SAST makes extensive use of intermediate files located in this project root directory. In some cases, you can achieve better performance for analysis by making sure this directory is on local storage rather than on a network drive.

Equivalent property name:
com.fortify.sca.ProjectRoot