In our project we use a jenkins job to build the files and folder needed in the installer. We use the synchronized folders function, because the contents may grow or change over time.
When a team member opens our Advanced Installer project without the correct files and folders build from jenkins in place, some files within the synchronized folders will be decoupled from its component, and will be automatically coupled to the main component "sunec.dll" (which is the java feature). Because of this, for example, the decoupled files (from its original component) will still be installed ,though in the wrong folder and even without the original component not selected as a feature during installation. Some files will also disappear.
All of this happens during the synchronization while opening the project. It gives no clear visible warning, only a small notification (and only if you have the notification view open). During a commit it is not really visible what you are checking in because of the many changes to "Installer.aip". Also all the Jenkins jobs will continue working, and the publish will likely also succeed because all the features are installed.
We encounter these problems with files under one feature.The files within another feature seems to not have this problem, and will still be coupled to their own component.
Is it possible to fix the hard coupling between the files and the feature/component. So if opened without the synchronized folders the installer.aip will still work, when the CI will build an installer with the synchronized folders.
FOLLOW US
Get the latest news in Application Packaging