You can license and configure the Multi-Language Pack by configuring the settings in the settings.properties file located in the installation directory.
Setting the License
You can set either a network or local license.
Network License
The network license is retrieved from Parasoft DTP. See Connecting to DTP information on how to connect to Parasoft DTP.
Local License
The local license password is provided by your Parasoft representative. To use a local license, edit the settings.properties file located in the installation directory and specify the following properties:
mlp.license.use_network=false mlp.license.local.password=<license-password>
Accepting the End User License Agreement
Set the following property to accept the Parasoft End User License Agreement (please read the EULA at https://www.parasoft.com/license):
parasoft.eula.accepted=true
Connecting to DTP
Configure your DTP settings to acquire a license and to send code analysis execution results to DTP. Specify the following settings in the settings.properties file located in the installation directory:
dtp.url
Specifies the URL to your DTP server. Remember to include the https://
protocol; DTP requires https://
connections from other Parasoft tools.
dtp.user
Specifies the username for DTP authentication.
dtp.password
Specifies the user password for DTP authentication. You can encode your DTP password by running the multilanguage-pack.sh or .bat with the encodepass parameter
. For example:
./multilanguage-pack.sh -encodepass mypassword
dtp.project
Specifies the name of the existing DTP project that you want to link to. This setting is optional for running the Multi-Language Pack, but required if you want to view results in DTP.
Example:
dtp.server=myhost dtp.port=8443 dtp.user=admin dtp.password=admin dtp.project=my_project
See Additional Configuration for more configuration options.
Connecting to Source Control (Optional)
Connecting to source control allows you to leverage the Multi-Language Pack to determine the authors of reported violations. With source control settings properly configured, the Multi-Language Pack can query for authors of the code lines where defects were detected by the static code analyzers.
To connect to source control, specify your source control system-specific settings in the settings.properties file located in the Multi-Language Pack installation directory. See Additional Settings for the list of source control settings.
The following example shows the settings required to connect to Git:
scontrol.rep.type=git scontrol.rep.git.url=https://mygit.mycompanycom/myrepo/myrepo.git scontrol.rep.git.branch=master scontrol.rep.git.workspace=c:\\development\\workspace\\JavaScript\\myrepo
Shallow Clones
If you are going to retrieve authorship information from Git, the cloned repository should not be shallow. A Git repository is considered shallow if the file .git/shallow
exists. Git may not accurately produce authorship data when checking out shallow clones from a repository. You should check out full clones to retrieve accurate authorship information.