About jlevac

jlevac · ‎Jun 13, 2018

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.

jlevac · ‎Jan 03, 2018

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

jlevac · ‎Oct 16, 2017

I'm also seeing the same Issue in Windows 2016. A java process remains after successfully running the uninstaller. Note that this java process was spawned by the uninstaller, not the application being uninstalled. Something holds a lock on the jre folder (presumable the java process). Once I manually kill the process, I am able to remove the jre folder. The uninstall logs are reporting a successful removal of the folder, but the jre folder still remains. Uninstall Folder: C:\Program Files\FOLDER\jre Status: SUCCESSFUL I'm assuming this is an InstallAnywhere bug. We are using InstallAnywhere 2017.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Re: Merging different version of the *.iap_xml

Merging different version of the *.iap_xml

Same Issue

Re: Merging different version of the *.iap_xml

Merging different version of the *.iap_xml

Same Issue