In our environment all atoms have effective.build.number=65087. But the Install4j Build Version is varying.
Atom Build Version for all Atoms is: 65087.
The version of Install4j for Atoms installed on Oct 28 2015 was 6.0.2 and install4j build version was : 6072
The version of Install4j for Atoms installed on April 12 2016 was 6.0.4 and install4j build version was : 6130
The version of Install4j for Atoms upgraded on May 13 2016 was 6.1 and install4j build version was : 6243
As Atom updates are pushing By Atmosphere Platform periodically based on Release control -All Atoms have same Build version(Number).
Where as why we don't have same Install4j Version and Install4j Build Version across all the atoms and molecules.
I am assuming as i4jruntime.jar, user.jar are installed as part of Atom installation. so they are managing locally and Atomshpere platform has no control on the Install4j Build versions installed
Q.1) Is there any relation between Install4j Build Version and Atom build Version.
Q.2) Do you have any Install4j Build Version and Atom Build version Matrix.
Q.3)What are the updates,Patches,fixes we will get for each release of Install4j Build Versions.(Any release cycle--Release control) to follow like Atom Release control
Q.4) On what frequency we need to update our Install4j Build Versions.
Q.5) Provide the standard documentation to update Install4j build version
Q.6)As atom_install(64).sh script is able to identify the existing Java Version Installed on the server, why the atom_upgrade(64).sh is not identifying and installing a Fresh copy of JRE under /<Atom_Install_DIR>