win_installer

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Adding in a java program, to try and adress the database access problem through NSIS

    • -0
    • +55
    ./src/SQLQueryGenerator.java
Adding in a java program, to try and adress the database access problem through NSIS

    • binary
    ./src/SQLQueryGenerator.class
Working on finding a way to get the locations for the llid folders from the database in NSIS, will probably need to use a array header for NISIS

Updator now extracts all the xx.xml files required for flahs to $INSTDIR\jboss-4.0.2\server\default\deploy\lams.ear\lams-central.war\flashxml

Great Success! This is nice!

All language files for projects are now unpacking correctly, ie lams_blah/conf/language

Added date string utility so the date can be entered as a string, but can still be compared as a version in the registry in the form yyyy-dd-mm

Uses a date instead of a vertsion to check for newer language pack versions

Added backup functionality, existing language files are zipped to C:\lams\jboss-4.0.2\server\default\deploy\lams.ear\lams-dictionary.jar\backup\

Updator checks for existing newer versions than the current, then applies this version to the registry, it also checks if there is a lams version 2.x installed

Skeleton for the language pack updator

    • -0
    • +218
    ./src/language-pack.nsi
add caveat about wildfire

Added in all the neccessary licences from the list of libraries in "lams_build/assemble/lams.ear/"

For task LI-30

add readme.txt; readme.txt and license.txt now copied to instdir

rename file

update list of completed locales for 2.0 release

not part of this project

Fixed bug for Bug LI-33, now the uninstaller is deleyed for 10 seconds to ensure that JBoss is stopped before uninstallation begins

7za is required for installer.nsi to zip and unzip retained files

    • -0
    • +504
    ./zip/copying.txt
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

    • -0
    • +1422
    ./src/LAMS-Update.nsi
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

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

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

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