This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Merging different version of the *.iap_xml
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎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:
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:
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎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.
We are in the same situation and we are thinking of utilizing the static merge modules for the moment.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎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.
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.