Versioning

Each module in Ceptor PortalProtect is versioned. Every module contains a file .version which contains the build which the module was created from

The .version file is a java properties file containing name, value pairs.

Property build.version in .version contains a Ceptor PortalProtect version number using the template: <major>.<minor>.<release>.
 

Major is updated when PortalProtect is updated with major features. When this is updated is not expected for the configuration files to be backward compatible, but if at all possible this is attempted.

Minor is updated when PortalProtect is updated with minor features, e.g. new plug-ins, new features which do not influence other components. As with major updates 100% backward compatibility cannot be guaranteed.

Release is updated with each build of PortalProtect. Release is updated automatically to ensure that all builds are unique.

Generally, all components must have the same version in order to be 100% sure of compatibility but Ceptor PortalProtect is in most cases backward compatible, in such a way that new components can communicate with older components. There will simply be functionality which is not available if the version numbers are mixed.

Ceptor is designed to run 24/7 meaning you can upgrade servers in a cluster one at a time, and you can use older Agent versions and mix them with newer, although these agents might possibly have limited functionality.

Example of a .version file.

This file is found in the root of the Ceptor PortalProtect JAR files in the lib folder in the distribution.