Full name: com.parasoft.jtest:jtest-maven-plugin:2020.1.0:jtest This goal should be used as a Maven report. It collects the build data and executes Jtest with the configured parameters (see Configuring the Jtest Plugin for Maven). It is called at the end of the build session and collects the aggregated data of every project. The goal works as an aggregator, which means it is not tied to a build lifecycle phase. Attributes - Requires a Maven project to be executed.
- Executes as an aggregator plugin.
- Requires dependency resolution of artifacts in scope: compile.
- Since version: 1.0.0
| Name | Accepted values / data type | Since | Description |
|---|
| compilation | PlexusConfiguration | 1.0.4 | A description of manual configuration data (see Manual Customization of Compilation Data) | | compilations | PlexusConfiguration | 1.0.4 | A list of descriptions of manual configuration data (see Manual Customization of Compilation Data) | | config | String | 1.0.0 | The name of a built-in, DTP, or user-defined test configuration. User property is: jtest.config | | dataUpdate | String | 1.2.9 | Allows you to manually update compilation data collected from the build. User property is: jtest.dataUpdate | | exclude | String | 1.0.0 | Specifies a subset of files or packages from the selected resources that will be excluded from analysis. You can provide the qualified names or use Ant glob patterns to match more filenames. User property is: jtest.exclude | | excludes |
| 1.1.0 | A list of exclude parameters. User property is: jtest.excludes | | fail | true | false | 1.0.0 | Fails the build if any violation is reported. Default value is: false User property is: jtest.fail | | forceTestReportsImport | true | false
| 1.0.0 | Ensures that test results are imported from the default location if the Jtest Plugin fails to recognize the existing test plugin (for example, Surefire) in the Maven environment. Default value is: false User property is: jtest.forceTestReportsImport | | home | Path | 1.1.0 | Specifies the Jtest installation directory. User property is: jtest.home | | ignoredIds |
| 1.0.4 | A list of ignored compilation IDs. User property is: jtest.ignoredids | | include | String | 1.0.0 | Specifies a subset of files or packages from the selected resources that will be included during analysis. User property is: jtest.include | | includes |
| 1.1.0 | A list of include parameters. User property is: jtest.includes | | projectNameTemplate | String | 1.0.0 | The project name template. This parameter allows you to configure the pattern with the options [groupId], [artifactId], [version], and [basedir]. User property is: jtest.projectNameTemplate | | publish | true | false | 1.0.0 | Enables reporting results of local analysis to the DTP server. User property is: jtest.publish | | report | Path | 1.0.0 | Specifies the directory where the report will be created. User property is: jtest.report | | resource | String | 1.0.0 | Specifies the input scope for analysis. If no resources are specified, Jtest will analyze resources from every built project. User property is: jtest.resource | | resources |
| 1.1.0 | A list of resource parameters. User property is: jtest.resources | | settings | Path | 1.0.0 | An absolute or relative path to the *properties file that includes custom configuration settings. User property is: jtest.settings | | settingsList |
| 1.0.0 | A list of settings parameters. User property is: jtest.settingsList | | showDetails | true | false | 1.0.0 | Displays detailed progress information. User property is: jtest.showdetails | | showSettings | true | false | 1.0.0 | Prints the current settings and customizations. User property is: jtest.showsettings | | skip | true | false | 1.1.0 | Allows you to skip the Jtest execution phase. If set to true, only the jtest.data.json data file is generated. Default value is: false User property is: jtest.skip |
A description of manual configuration data (see Manual Customization of Compilation Data). - Type: org.codehaus.plexus.configuration.PlexusConfiguration
- Since: 1.0.4
- Required: No
compilationsA list of descriptions of manual configuration data (see Manual Customization of Compilation Data) - Type: org.codehaus.plexus.configuration.PlexusConfiguration
- Since: 1.0.4
- Required: No
The name of a test configuration. The following configuration types are supported: - built-in test configurations, for example
"builtin://Recommended Rules" - dtp test configurations, for example
"dtp://New Config" - user-defined test configurations, for example
"user://Your Config"
User-defined test configurations should be stored in the [INSTALL_DIR]/configs/user directory as *.properties files. - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.config
Allows you to manually update compilation data collected from the build. - Supported actions: prepend, append, and set.
- Supported data types: classpath, bootpath, sourcepath, resourcepath, binarypath, sourcecode (set only) and encoding (set only)
- Scope: all collected projects data will be updated
- Type: java.lang.String
- Since: 1.2.9
- Required: No
- User property:
jtest.dataUpdate
See Manual Customization of Compilation Data and Compilation Data Model for details. excludeSpecifies a subset of files or packages from the selected resources that will be excluded from analysis. You can provide the qualified names. You can use glob patterns to match more filenames. Example 1: The following pattern excludes all files from com.parasoft package and its sub-packages: /com/parasoft/** Example 2: The following pattern excludes all files from the package com.parasoft.jtest, but NOT from its sub-packages: /com/parasoft/jtest/* Example 3: The following pattern excludes all files from the given directory and all subdirectories: path:/home/user/project/src/test/java/** - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.exclude
excludesA list of exclude parameters. Can be configured by property since Maven 3.0.3. - Type: java.lang.String[]
- Since: 1.1.0
- Required: No
- User property:
jtest.excludes
failFails the build if any violation is reported. - Type: java.lang.String
- Since: 1.0.0
- Required: No
- Default: false
- User property:
jtest.fail
| Anchor |
|---|
| forceTestReportsImport |
|---|
| forceTestReportsImport |
|---|
|
forceTestReportsImportEnsures that test results are imported from the default location if the Jtest Plugin fails to recognize the existing test plugin (for example, Surefire) in the Maven environment. | Info |
|---|
| We recommend using this parameter with the "clean" goal to prevent the Jtest Plugin from importing test results from previous executions. |
- Type: java.lang.Boolean
- Since: 1.0.0
- Required: No
- Default: false
- User property:
jtest.forceTestReportsImport
homeJtest installation directory. - Type: java.io.File
- Since: 1.1.0
- Required: No
- User property:
jtest.home
ignoredIdsA list of ignored compilation IDs. Supported by Maven since 3.0.3. - Type: java.lang.String[]
- Since: 1.0.4
- Required: No
- User property:
jtest.ignoredids
includeSeocifies a subset of files or packages form the selected resources that will be included during analysis. You can use glob patterns to match more filenames. Example 1: The following pattern includes all files from com.parasoft package and its sub-packages: /com/parasoft/** Example 2: The following pattern includes all files from the package com.parasoft.jtest, but NOT from its sub-packages: /com/parasoft/jtest/* Example 3: The following pattern includes all files from the given directory and all subdirectories: path:/home/user/project/src/test/java/** - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.include
includesA list of include parameters. Can be configured by property since Maven 3.0.3. - Type: java.lang.String[]
- Since: 1.1.0
- Required: No
- User property:
jtest.includes
| Anchor |
|---|
| projectNameTemplate |
|---|
| projectNameTemplate |
|---|
|
projectNameTemplateThe project name template. By default, the following pattern is used to create project names in json: :"groupId:artifactId ". This parameter allows you to configure the pattern with the options [groupId], [artifactId], [version] and [basedir], for example, to make a project name compatible with the project name in Eclipse. | Warning |
|---|
| If you change the pattern for a project that has already been integrated with DTP, DTP will not recognize your project. It will assume that your project after the change of the pattern is a different project. For details, see the DTP documentation. |
- Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.projectNameTemplate
publishEnables reporting results of local analysis to the DTP server. - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.publish
reportSpecifies the directory where the report will be created. By default it is ${project.build.directory}/jtest. - Type: java.io.File
- Since: 1.0.0
- Required: No
- User property:
jtest.report
resourceSpecifies the input scope for analysis. If no resources are specified, Jtest will analyze resources from every built project. Use the following pattern to specify the paths: ${ProjectName}/my/src/dir/my/package/file.java". You can use the following wildcards: - ? - matches one character
- * - matches zero or more characters, except the path separator (the / character)
- ** - matches entire paths, including the path separator (the / character)
 The Jtest Plugin for Maven resolves ${ProjectName} to ${artifactId}:${groupId}.
- Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.resource
resourcesA list of resource parameters. Can be configured by property since Maven 3.0.3. - Type: java.lang.String[]
- Since: 1.1.0
- Required: No
- User property:
jtest.resources
settingsAn absolute or relative path to the *properties file that includes custom configuration settings. | Info |
|---|
| Some of the setting names may not be consistent with the settings dedicated for the build system plugins. See Configuration Settings for details. |
- Type: java.io.File
- Since: 1.0.0
- Required: No
- User property:
jtest.settings
settingsListA list of settings parameters. Supported by Maven since 3.0.3. Can be configured by property since Maven 3.0.3. - Type: java.io.File[]
- Since: 1.0.0
- Required: No
- User property:
jtest.settingsList
showDetailsDisplays detailed progress information. - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User Property: jtest.showdetails
showSettingsPrints the current settings and customizations along with the information where each of them is configured (e.g. in the jtest.properties file). - Type: java.lang.String
- Since: 1.0.0
- Required: No
- User property:
jtest.showsettings
skipAllows you to skip the Jtest execution phase. If set to true, only the jtest.data.json data file is generated. - Type: java.lang.String
- Since: 1.1.0
- Required: No
- Default: false
- User property:
jtest.skip
|