We were using the build time stamp for our version number with the format:
and found that with the new year, the yy now overflows an internal toInt conversion, causing the module install to fail (Exception parsing module).
but found that the older version, with the higher build number, was archived in the gateway and was always being loaded in lieu of the the newer one. (Yes, we could have changed other portions of the version number). The jar files remained even when the module was removed. We had to shut down the gateway and manually delete them. Is there a better way to manage this?
We realized that the new format would regularly put us into this situation, so we now use the julian date instead of MM/dd to keep the build number shorter than the overflow size of integer: