Prioritize - The Behavior of the Command Line Argument "analyzeMultiModuleExclusions"
Mend supports multi-module analysis as part of the Mend Prioritize offering. The command-line argument “analyzeMultiModuleExclusions” is one of the parameters that can be configured during the step of creating a setup file.
To learn more details on what is a setup file and the full list of parameters, please see this documentation: Scanning with Multi-Module Analysis
Description
Multi-module analysis can include exclusion rules to support automatic/default and manual exclusion of files that should not be considered by the Unified Agent as valid ‘appPath’ candidates.
This parameter enables users to specify patterns for file names that should not be analyzed.
List of files that can be used as ‘appPath’ candidates. e.g. package.json, project.jar, etc.
To check the full list of the file for each language, please refer to this documentation: Scanning Projects with Mend Prioritize | Running-the-Unified-Agent
There must be two or more ‘appPath’ candidates in the same folder in order for this parameter to work. For example, if you have only 1 myapp-v8.1.0.jar, using analyzeMultiModuleExclusions wouldn’t affect anything and nothing will be excluded. However, if you have both myapp-v8.1.0-internal.jar and myapp-v8.1.0.jar. in the same directory, the following command would ignore myapp-v8.1.0-internal.jar:
CODEjava -jar wss-unified-agent.jar -d ./ -analyzeMultiModuleExclusions '**/*internal*' -analyzeMultiModule multimodule.txt