When examining analysis units in CAST MS after a delivery, analysis units are shown in CAST MS as added when DMT shows that the analysis units are ignored as shown in the screenshots below.
CAST-MS shows both projects:
DMT settings are to exclude Java projects when a Maven project exists as shown below:
Project is shown as ignored in DMT as shown below:
Release | Yes/No |
|---|---|
| 8.3.x |  |
RDBMS | Yes/No |
|---|---|
| CSS | |
Below is the step-by-step scenario leading to the problem:
- Deliver code in DMT
- Examine analysis units in CAST MS after DMT Delivery process
The impact of the problem on the analysis or the dashboard is: No impact
To fix the problem, proceed as follows:
- Unselect the analysis unit for analysis if you do not want it to be analyzed
The reason that this can show up is that the excluded project is required by other projects, that depend on it. So, to insure that the analysis will be complete in CAST-MS, the corresponding analysis unit is imported, even if it has been explicitly excluded. This is an expected behavior with CAST.
This can be verified by examining the validation_report.pmx in the DMT files in the delivery area for the version of the package being delivered. It will show if it is referenced as shown in the screenshot below:
