This page provides information about excluded projects compared with last version when the source code has not changed / when these projects are not expected to change.

Release
Yes/No
8.3.x(tick)
8.2.x (tick)
8.1.x (tick)
8.0.x(tick)
7.3.x(tick)
RDBMS
Yes/No
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
  • Package a version V2 of a J2EE application.
  • Check the Package content : You see that the Compared with last version column is not "Existing" but "Removed" like below example :

  1. In CAST MS, in the Delivery tab, select the last version that has been packaged and click on the "Manage the delivery button".


  2. Once the DMT is opened, select the culprit package and go to the Package content tab, select the Project type where there is "removed project" and check whether the name of the project is removed.


  3. Check if project type of the project is supported by CAST :
    1. Open a pom.xml file that is removed, and check for : <packaging> :
    2. The supported packaging values are :

      1. Default maven

      2. jar

      3. war

      4. ejb

      5. ejb-client

      6. some specific ones that we know are compatible with the default :

        1. sonar-plugin

        2. maven-plugin

        3. bundle

    3. For the packaging not supported, you will see information message in the discovery log file informing you that the project is ignored because the type of package is content-package :


  4. Open the Delivery Folder and navigate to the Package folder corresponding to the last version as explained in Delivery Manager Tool - Information - DELIVERY Folder Structure and Contents page.
  5. Open the discovery log file and check if there is information message or warning message about the project being ignored and the reason why it is ignored. Navigate to the page Delivery Manager Tool - Discovery - Warning to check the type of message that may lead to this behaviour.
  6. Check if the issue is linked to the DMT Configuration :
    1. Open the Delivery Folder and navigate to the Package folder corresponding to the compared version as explained in Delivery Manager Tool - Information - DELIVERY Folder Structure and Contents page.
      1. Open the config.DmtDiscovery file for the two versions of the delivery and compare them. The result will be as shown below:

        In the above example, a discoverer has been unselected : The discoverer is Java files per package folder.

      2. Compare the 2 DMT : For this example, in the DMT we can see that the discover has been unselected as shown below, compared to the previous version.


      3. Check all the differences between the two versions. Check also the plugins used. To do that, in the Delivery folder, go to the Version level for the two versions, and open an *.entity.xml file (same name for both version) and compare the discoverer version installed as below :
        The part to take into account is :

        If there is differences, it may explains the reason why there is removed projects.
  7. If none of these steps help to resolve the behaviour, contact CAST Technical Support and provide Relevant Input to help CAST Technical Support team investigate and solve your problem.