This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jlevac
Level 3
‎Jan 03, 2018 02:17 PM

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:



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.

Thanks,
JP
Labels (1)
Labels
0 Kudos
(2) Replies
Techmaddy
Level 3
‎Jun 13, 2018 04:50 AM

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.
0 Kudos
jlevac
Level 3
‎Jun 13, 2018 09:45 AM

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.
0 Kudos