I'm upgrading several projects from 12.3.1 to 12.8, as well as a few other changes. It would appear there are migration problems.
To do this work I created a gitHub feature branch and cloned it to a different path than the master project. So the path changed. But now I cannot get it to build.
Questions:
1. Did a Convert Paths on each project in 12.3.1 before migrating to 12.8 and made sure ALL paths had a Project Variable.
2. If AI removes files because of path issues, then re-adds them, they get new UUIDs. That will cause upgrade problems won't it?
3. When building from the command-line it shows the error "The source folder D:\staging\dovue" of the synchronized folder "APPDIR" is missing from disk. ...". But that Project Variable is actually D:\git\docvue\dve\installers\staging\docvue and it resolves correctly in AI interactively. The project root is D:\git\docvue\dve\installers\projects. And the project is set to use relative paths. Why can it not resolve the same paths when run from the command-line???
4. I cannot seem to save Path Variables (Project Variables) to a file anywhere. I go through the motions but no file is ever written to the path displayed in the dialog. Even to the directory containing the project's .aip file. And it's the same with 12.3.1, 12.7.2 and 12.8. There are only 2 "Project Variables", which are in the .aip, and no Custom Variables. Is that why no file is produced? How does that actually work?
Observation: Looking in the 12.3.1 .aip file it had relative paths for caphyon.advinst.msicomp.AppPathsComponent like ..\staging\docvue. But after building from the command line with 12.8 that path turned in to ..\..\..\..\..\..\staging\docvue which is the root of drive D:. Seems like a bug!
5. We use TeamCity + GitHub for automated builds in a dynamically-generated directory (on C:). AI is executed from an ant build.xml. And we use that same server to AI development on a separate hard drive than where TeamCity runs. How can paths be handled for those 2 situations? This wasn't an issue with 12.3.1, but 12.8 fails with path problems.
At this point we cannot build successfully.
Another question:
a. Organization with added files: We added a JRE to the root directory, e.g. APPDIR/jre. And our product has features with subfeatures. When AI scans for additions it places hundreds of new entries in the root of a feature, not the designated Current Feature. That requires long painful movement of each individual entry to the correct subfeature so if the user does not choose to install everything it is in the right place. Why does it not use the Current Feature when adding new files??? Is there any way to avoid moving hundreds of entries by hand??
I will email the primary project file to AI support.
FOLLOW US
Get the latest news in Application Packaging