Set this property to "True" if this Files bean includes a JAR file(s) that makes use of version numbers. If set to "True", then at build time, the builder checks each specified file to determine if it is a JAR file. If so, it loads the JAR's manifest and looks for the "Implementation-Version" property within the manifest. At runtime, It compares the JAR version of the file being installed with the JAR version of the file already on the target machine to determine which one is newer. It then decides whether to replace the file based on the value of the Replace Option property of the parent component.

Version comparison is done based on the Implementation-Version format specification documented at http://java.sun.com/j2se/1.4.1/docs/guide/plugin/developer_guide/version_format.html.

According to that specification, the basic format should be n1.n2.[n3][_<patch_number> | -<milestone_name>] where n1, n2 and n3 must be numeric, and the patch_number or milestone_name can be alphanumeric. If n1, n2 or n3 (if it exists) are not integers, then no JAR version comparison will be performed. When present, the patch_number and milestone_name parts are always compared case sensitively as strings.

IMPORTANT: This only works if you are running with a Java 2 JVM. If you are running with a Java 1.1 JVM, the JAR version checking is skipped. Additionally, in order to use JAR version checking, your ISMP builder/IDE must be run using a Java 2 JVM.