Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0
-
Fix Version/s: 5.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
I intend to introduce upgrade handling in IzPack into discussion.
Major requirements that might be provided:
- get the installation path of a previous installation of the same component
- get the version of the same component installed before
- check the compatibility of the previous component version with the one coming with the upgrade setup and deny installation in case of incompatbilities
- decide which settings of a previous installation should overwrite the default settings in the new installation (including property+INI+XML files, registry), optionally depending on the source and target version, and patch the default settings coming from the new installation accordingly (comments should be saved).
- delete obsolete files from an old installation, even if they had been installed in a different root path.
Note:
To not get lost in e-mail discussions I rather create a task here that refers to single sub-issues, that might be done for this purpose. This should not replace the developer discussion, but should be the central point for tracing the progress of this abstract issue.
Issue Links
| This issue supercedes: | ||||
| IZPACK-295 | Installer support of Win Setup API - replacing blocked files after reboot |
|
|
|
| IZPACK-519 | Dynamic variable enhancements |
|
|
|
| IZPACK-526 | Add merging and patching of configuration files and registry entries |
|
|
|
| IZPACK-525 | Enhance conditions to be creatable from dynamic variables to get more dynamic conditions |
|
|
|
| IZPACK-537 | Refresh dynamic variables also at the beginning of the installation to be able to use them for installerrequirement conditions |
|
|
|
Implemented and documented so far - see IzPack User Documentation