Description
 This page explains how to troubleshoot the issue when a J2EE project is excluded by the Delivery Manager Tool when using the JEE File Discoverer. 
Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
Step by Step Scenario
  1. Create an application with the JEE File Discoverer installed.
  2. Run packaging and Delivery.
  3. Accept Delivery and set as current version.
  4. Run analysis.
  5. Check the results to see that no java files have been analyzed. 
Action Plan

The JEE File discoverer is used in cases where a .project or .pom.xml file is missing in the source code.

In such cases, you will come across the below messages in the selection.castlog2 file located in the Delivery folder corresponding to the source package after delivery.

Steps to follow if you have these messages - 

  1. Open the validation.CastProjects from the source package in the Delivery folder and search for the project that is excluded. From the above example, we take "lib"

                   

                   You will see the selectionStatus as "Excluded"

      2. When checking the <Metadata> tags, you see there is one name as "incompletePackage". 

                   

          This mentions that the project has been excluded because it is an Incomplete Package.

Please Note: The same is applicable for the Unnamed Package.

     

          To solve the issue,  you need to uncheck the respective rule in the package configuration in the Delivery Manager Tool and then proceed with the packaging/Delivery.

                   


Impact on Analysis Results and Dashboard

Files are not analyzed and hence wrong dashboard results. 

Notes/comments
 # 29910
Related Pages