Delivery Manager Tool - Package - Validation - Alerts - J2EE - Maven - Missing projects

This page explains how to troubleshoot missing project alerts for J2EE applications. 

1. In the list of alerts "Missing projects", if the Alerts are like [name1][name2] it means that the DMT has found a missing project (maven project or Eclipse project) which is refered by the poject file :
   
   In the above example the project named rar/brcore is missing.
   1. Open the project file of the file defined in the project path, in this example it is a maven project that is in : COMMON_CHECKOUT/trunk/sales-TKB/TKB-core/pom.xml. Check the reference to the project named rar/brcore.
      
   2. Once the check is done, check if this project rar/brcore really exists in the packaged source code.
   3. If it does not exist :
      1. Check if the missing project has been packaged in another package of the same version:
         1. If yes, you have to solve this alert with a manual remediation by pointing to the missing project and running the packaging.
         2. If no, then this alert is expected.
   4. If it exists, to solve this alert you have to remediate manually this missing project alert
2. If the missing project alert is like [${variable}{project name}] as shown in the below screenshot, it means that a variable has not been resolved:
   
   1. Check if this is an Undefined variable alert.
   2. If yes, check that the variable which is not resolved is in the list of undefined variable alert.
   3. If it is, remediate this undefined variable and package the source again.
   4. If it is not, open the pom.xml file and replace the variable by its true value.
      
      
3. Check if the alerts are like [name1][name2]:<version> as shown in the below screenshot :
   
   In the above example, the project name is venibe-provider-cxf and it is refering to an artifact [org.apache.cxf][cxf-rt-transport-http]:3.0.3 which is missing. It is a jar file which is not found.
   1. If there is no type of packaging listed in the pom.xml as in the screenshot below, then a jar file is expected for a dependency by default:
      
      
      1. if you have as well a pom type dependency in the pom.xml as in the screenshot below;
         
         Then this is an currently unsupported case as the type of dependency of pom type is currently not supported by CAST, though may be supported in a future release.
         1. As a manual workaround, gather all the associated jar files in the dependency lines of the pom.xml referenced in the alert, then add them in a file system package, and then finally add these jar files to the analysis unit's class path so that they can be properly found.
   2. Otherwise check if the missing jar exists in the source code packaged.
   3. If it does not exist, getting this alert is expected
      1. You have to create a package : Automated extraction of required jar files which will point to a maven repository where the jar file exists.
      2. Run a package on the full version.
   4. If it exists :
      1. Check if the version of the jar file is the correct one.
4. If the above steps do not help you, contact CAST Technical Support with the Relevant Input in order to reproduce the issue.

 Relevant Input

• Delivery Manager Tool - Relevant Input
  
• Screenshot showing the alerts
• In case of missing ressources / files / objects, provide a screenshot showing that these items exist.