CMS Application - Analysis - Java version set at application level doesn't reflect at job level

If the Java version used for the analysis is changed at the application level the same will not be reflected to the job level.

When the java source is discovered with the DMT. DMT decides the java version for few of the analysis units based on the configuration used in the project files.
This mainly occurs because the MAVEN discoverer sets by default the java version to 1.5 when no version of compiler is explicitly configured in the pom.xml.

 For all these Analysis units the java version parent is not the application level java version.

So we cannot change the java version of these analysis units by changing the java version at the application level. 

To change the java version of these analysis units we need to manually change the version in each and every java analysis unit.

This problem will be fixed in the CAST AIP version 7.3.5.