CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - JAVA128 Annotations are not managed in Environment Profiles

While running JEE analysis using JEE analyzer you may get warnings related to Annotation 'xx.xx.xx.xxx' is not managed in Environment Profiles as shown below:

2018-11-08 06:56:49.758242	  Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.bind.annotation.XmlType' is not managed in Environment Profiles		
2018-11-08 06:56:49.759243	  Warning	MODULMSG ; Job execution	JAVA128: Annotation 'com.google.common.annotations.TestWS' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	  Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.jws.soap.SOAPBinding' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	  Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.bind.annotation.XmlRootElement' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	  Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.ws.BindingType' is not managed in Environment Profiles

Below is the step-by-step scenario leading to the problem:

1. Package and deliver the application.
2. Set as current version.
3. Run the analysis.
4. Check the analysis log file.

5. Warning "JAVA128: Annotation 'xx.xx.xx.xx' is not managed in Environment Profiles"

You may get these type of warnings due to two possibilities

1. When you have the annotation references in the source code.
   1. You need to manage the environment profile to support the annotation. Please refer this page : Manage annotations
      
      
2. When you do not have any references to the annotation in the source code.
   1. Pick an example warning from the analysis log like, JAVA128: Annotation 'java.beans.ConstructorProperties'
   2. Search for the pattern @ConstructorProperties in the source code. If there is no reference to it then you can ignore the warnings. They are coming from our(CAST) jars and it seems to be random and need to be ignored as there will be no impact on the analysis.
      
      
3. If the previous steps do not solve the issue, then contact CAST Technical Support, with the Relevant input in order to reproduce the issue.

The issue of false warnings even though the annotations are not used in the source code is planned to be fixed in JEE 1.0.19