Resolving package conflicts

If you have customizations or a localized product, you might run into some issues when applying a package, such as a patch. This topic contains information about how to resolve conflicts if they occur.

About this task

Some packages might contain components that override existing components in your Rational® Change installation. Sometimes applying the package results in conflicts which must be resolved.

For example, suppose you have installed the CustomizationPackage, and this package contains a customized version of an attribute control. Then, you receive PatchPackage, and this package contains a fix to the original attribute control. You want both the fix and the customization. However, regardless of the order the packages are applied, you have the customized control or the fixed control, but not the fixed customized control. The last package installed overwrites the conflicting file.

Follow these steps to ensure that you have the fixed customized control.

Procedure

To resolve package conflicts:

Update CustomizationPackage to be baselined off the attribute control in PatchPackage.
The customization must be reapplied to the patched version of the attribute control.
Install CustomizationPackage on top of (after) PatchPackage.
Similarly, after a globalization has been installed, you might receive a patch that introduces additional resource strings that have not been localized. These resource strings are typically located in a properties file under patch_dir/wsconfig/messages. In this case, augment the patch to include a localized properties file before applying it.