main/cli_ure/readme.txt

24 After a release the entries in cli_ure/version/version.txt must be changed to reflect the versions
64 Step 3: Determine the versions of the assemblies
70 Step 4: Changing the versions in the cli_ure module.
80 The versions may already have been incremented because someone has changed code after the
103 Step 5: Changing the versions in the unoil module
106 of unoil/climaker/version.txt similar to the versions.txt in this module. Then rebuild the module
126 The versions of all assemblies are contained in cli_ure/version/version.txt. This is the place where
127 the versions are changed. This will happen under two circumstances. First, the versions are
128 adjusted AFTER an office was released. The version.txt must then contain the versions at the
136 cliureversion.mk contains all the entries of version.txt. The versions have been incremented
162 CLI_URETYPES_OLD_VERSION represents a range of former versions (which were compatible).
174 about how the versions have to look like.
209 is run which creates the cliureversion.mk with the new versions. This automatism only changes
210 the version parts which have the meaning of a compatible change. Which versions are to be
224 For example, the versions in version.txt are:
234 As one can see from the incversions.txt, the versions of the cli_ure.dll and cli_cppuhelper.dll
238 Further notes on increasing the assembly versions
245 When changing a version of an assembly then the versions of the assemblies which depend on it shoul…
246 be changed as well. For example, when changing the version of cli_uretypes.dll, then the versions o…
250 If one would not change the versions of the dependent dlls then one would risk that an assembly