Community Forums
Results 1 to 3 of 3

Thread: Merging different version of the *.iap_xml

  1. #1
    Join Date
    Oct 2017

    Question Merging different version of the *.iap_xml

    I'm wondering if anyone has successfully implemented a strategy for merging iap_xml files with version control tools such as git.

    These "xml files" are extremely difficult to merge across branches since they spit out a lot of random numbers which are changed every time the file is saved. For example:

    <object class="com.zerog.ia.installer.Installer" objectID="73005c37b664">

    The objectID will often change, causing tons of merge conflicts, even though we've made no modifications to that particular piece of the installer.

    I'd love for Flexera to implement some kind of persistent objectID to avoid these crazy merge conflicts, or have some kind of guideline to properly merge these files.


  2. #2
    Join Date
    Jan 2009
    Were you able to find any solution to the problem.

    We are in the same situation and we are thinking of utilizing the static merge modules for the moment.

  3. #3
    Join Date
    Oct 2017
    We have not found a version control solution for this file.

    So far, we've been using 1 VM for modifying the iap_xml file and "locking it" while InstallAnywhere work is made. This ensures only one person can modify this file at a time. Once the modifications have been merge back into the main branch, the VM is unlocked.

    Not an ideal process since we can't work on the Installer in multiple branches.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts