lams / win_installer

src

Tools

Line History

Line Count Graph
Line Count Graph

Stats

Commits this week: 0
Total Committers: 3
Last Commit:
Commits this week: 0
Total Lines of Code (LoC): 0
Net change in LoC this week: 0

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Friday 15 Dec 2006
7:12 am

lfoxton

Now have names for all the llid file folders

Options
    • binary
    ./language-pack.nsi
Thursday 14 Dec 2006
2:50 pm

lfoxton

Now have names for all the llid file folders

Options
    • binary
    ./language-pack.nsi
1:44 pm

lfoxton

Can now get multiple rows from the database using an array utility i found on the net. All that is needed now is to make the correct llid directories and put the required language files in

Oh, and update the database with the new language files

Options
    • binary
    ./Array.nsh
    • binary
    ./Array.nsi
    • binary
    ./language-pack.nsi
12:09 pm

lfoxton

Finally found a way around the sql database query problem, now i can get single values from the db for the llid, still havent thought of a way to get multiple entries

Options
    • binary
    ./language-pack.nsi
9:43 am

lfoxton

Adding in a java program, to try and adress the database access problem through NSIS

Options
    • -0
    • +55
    ./SQLQueryGenerator.java
9:23 am

lfoxton

Adding in a java program, to try and adress the database access problem through NSIS

Options
    • binary
    ./SQLQueryGenerator.class
    • binary
    ./language-pack.nsi
Wednesday 13 Dec 2006
1:56 pm

lfoxton

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

Options
    • binary
    ./language-pack.nsi
10:19 am

lfoxton

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!

Options
    • binary
    ./language-pack.nsi
9:42 am

lfoxton

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

Options
    • binary
    ./language-pack.nsi
7:01 am

lfoxton

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

Options
    • binary
    ./language-pack.nsi
6:34 am

lfoxton

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

Options
    • binary
    ./language-pack.nsi
Tuesday 12 Dec 2006
4:10 pm

lfoxton

Added backup functionality, existing language files are zipped to

C:\lams\jboss-4.0.2\server\default\deploy\lams.ear\lams-dictionary.jar\backup\

Options
    • binary
    ./language-pack.nsi
3:51 pm

lfoxton

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

Options
    • binary
    ./language-pack.nsi
12:44 pm

lfoxton

Skeleton for the language pack updator

Options
    • -0
    • +96
    ./Functions.nsh
    • binary
    ./language-pack.nsi
Tuesday 05 Dec 2006
10:03 am

jliew

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

Options
    • -9
    • +7
    ./installer.nsi
  2. … 1 more file in changeset.
10:02 am

jliew

update list of completed locales for 2.0 release

Options
    • -1
    • +1
    ./lams2.ini
7:22 am

jliew

not part of this project

Options
    • binary
    ./LAMS-Update.nsi
Monday 04 Dec 2006
2:44 pm

lfoxton

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

Options
    • -17
    • +16
    ./installer.nsi
1:24 pm

lfoxton

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

Options
    • binary
    ./LAMS-Update.nsi
    • -20
    • +52
    ./installer.nsi
Friday 01 Dec 2006
12:30 pm

lfoxton

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

Options
    • -103
    • +64
    ./installer.nsi
    • -24
    • +6
    ./uninstall.ini
7:14 am

lfoxton

Output suppression added to prevent stutus bar popus from appearing duiring install

Options
    • -5
    • +5
    ./installer.nsi
6:46 am

lfoxton

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

Options
    • -12
    • +14
    ./installer.nsi
    • -3
    • +3
    ./uninstall.ini
Wednesday 29 Nov 2006
9:30 am

lfoxton

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

Options
    • -2
    • +3
    ./installer.nsi
7:39 am

lfoxton

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

Options
    • -15
    • +23
    ./installer.nsi
Tuesday 28 Nov 2006
2:39 pm

lfoxton

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

Options
    • -9
    • +19
    ./installer.nsi
12:35 pm

lfoxton

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.

Options
    • -12
    • +24
    ./installer.nsi
10:12 am

lfoxton

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

Options
    • -10
    • +81
    ./installer.nsi
    • -6
    • +32
    ./uninstall.ini
    • -46
    • +0
    ./uninstall_back.ini
Friday 24 Nov 2006
1:28 pm

lfoxton

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

Options
    • -8
    • +13
    ./installer.nsi
12:51 pm

lfoxton

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
    • -44
    • +37
    ./installer.nsi
10:10 am

lfoxton

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

Options
    • -11
    • +35
    ./installer.nsi