installer.nsi

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changes to the win_installer project as of 2.1:

Project is split up into smaller sections:

- installer

- updater

- utils

- language pack

- start lams

- stop lams

- backup lams

- restor lams

- java

  1. … 122 more files in changeset.
[LI-54] - Support the XAMPP location of the my.ini file

[LI-54] Checks for my.ini in C:\Windows to support Xampp bundles mysql installation

[LI-55] * Change the language pack and future installers to add a "\" to the path before trying to call mysql. * Change future installers to add the "\" automatically before saving in the registry.

  1. … 1 more file in changeset.
Deletes registry entries if there is a failed installation

[LI-36] New java wrapper 3.2.3 for installer.nsi

  1. … 26 more files in changeset.
Inserting license-wrapper.txt into $INSTDIR for the java wrapper 3.2.3

  1. … 1 more file in changeset.
Added "or 1.6" to this message

Could not verify Java JDK 1.5, please check your JDK directory.

[LI-45] Does a check for the java version in the registry, will work for 1.5 or for 1.6. Also checks if teh javac compiler version is 1.5 or 1.6

[LI-45] Does a chack for the java version in the registry, will work for 1.5 or for 1.6. Also checks if teh javac compiler version is 1.5 or 1.6

Fixed a bug that stopped the database being removed on a failed install

[LI-39] Set the default server sytem admin user's locale to the one chosen in the installer, so it displays in the correct language on startup

  1. … 1 more file in changeset.
[LI-36] lamsdump.sql is now copied properly

LI-38: Changed the function .inInstFail so it only dletes the files created by the failed installation (not retained files) and it removes the db which was made by teh failed install

undo of changes made by an accidental commit

Calling sql scripts to update the db with the new languages

  1. … 1 more file in changeset.
add readme.txt; readme.txt and license.txt now copied to instdir

  1. … 1 more file in changeset.
Fixed bug for Bug LI-33, now the uninstaller is deleyed for 10 seconds to ensure that JBoss is stopped before uninstallation begins

The un-installer now retains uploaded files, repository and database in a zipped which can be unpacked on a re-install. This is don using 7za.exe

  1. … 1 more file in changeset.
Altered the installer to keep only database, repository and uploaded files, kept in a folder called 'backup' and restored to the respective firectories on re-installation

Could not yet find a way to compress and decompress folders using only NSIS and/or windows built-in functions, it would be good to compress the retained files for storage

  1. … 1 more file in changeset.
Output suppression added to prevent stutus bar popus from appearing duiring install

Changed some prompting and output information to be more user friendly, Prompts the user on which files to keep instead of which files to remove on uninstall etc

  1. … 1 more file in changeset.
Fixed bug: It did not delete the retained files on re-install if the user chose that option, now it does

Fixed bug: It did not delete the retained files on re-install if the user chose that option, now it does

Options on uninstall to retain repository, uploaded files and config files have been made functional, still need to dump the database if it is to be retained

The retained files are stored back in the intsall directory with the same file system as before the un-installation, all other files are removed

Completed the rebuild of the retained database on reinstall, more thorough testing required, but as far as i can tell this closes issue [LI_32]

1. Modify uninstaller screen to clarify retaining files on uninstall

2. Modify uninstaller to keep:

a. lams database (possibly dumped into a backup file, and removed from the 'live' database)

b. content repository files (nominally in c:\lams\repository)

c. configuration files log4j.xml and server.xml

3. Modify installer to detect and use these existing files - may need to keep a registry entry when uninstalling, so that this can be checked easily.

Re-install option completed User can now retain old files like the configuration and repository on a re-install Still need to restore the database

  1. … 2 more files in changeset.
Unistall operations comleted, user can now retain database, repository, uploaded files and configurations

Files are saved into install directory

Not yet implemented: On re-install check that the retained files folder exists and add files for the installation

Unistall operations comleted, user can now retain database, repository, uploaded files and configurations

Files are saved into a directory at C:\lams_RetainedFiles

Not yet implemented: On re-install check that the retained files folder exists and add files for the installation

Options on uninstall to retain repository, uploaded files and config files have been made functional, still need to dump the database if it is to be retained

The retained files are stored back in the intsall directory with the same file system as before the un-installation, all other files are removed