The purpose of this page is to provide information on certain cases which may cause extra analysis units to be created in CAST Management Studio (CMS). 

There are situations where the number of analysis units in the delivery process shown in the summary screens and the number of analysis units that show up in CMS are not the same. 

For example, 5 analysis units are selected and 4 ignored after packaging in DMT as shown below:

But when looking later in CMS, 7 analysis units can be seen:

Applicable in CAST Version
8.0.x (tick)
7.3.x (tick)
Applicable RDBMS
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
Action Plan

The reason for this is that the status displayed in the DMT results are from the Selection phase, and these results can be altered during the Validation phase, because some Excluded projects may be referenced by Selected ones, so they need to be imported into CAST-MS. Therefore, even an Ignored project may be imported into CAST-MS.

A case where this could happen is if there is a mix of Eclipse and Maven projects in one source code location with some projects having just an Eclipse project, some projects having just a Maven project, and some having both a Maven and an Eclipse project.  If the discovery options are set to select Eclipse by default and ignore Maven projects when both Eclipse and Maven are present,

and if

  • project A has both an Eclipse and Maven project so that the Maven project A is initially ignored.
  • project B has only a Maven project which depends on the ignored Maven project A.


  • the ignored Maven project A would be altered during the validation phase to be included and would be imported into CMS for consistency.

 Ticket # 5580

Related Pages