This page is a short record of the database changes, changes to configuration files (anything under lams_build/conf) and lams-www changes. This will be used as the basis for updates for the installers/upgraders, so any changes not recorded here may not make the upgrader.

Originally this page was only for db updates but from 2.1 onwards it will have the configuration and lams-www changes.

Since RC1

Since RC1 Oct 20th

Since RC2 Nov 5th

Since November 22nd

From LAMS 2.0 to LAMS 2.0.1 Beta (lams2_0_1_beta 22 Feb 07)

From LAMS 2.0.1 Beta to LAMS 2.0.1

From LAMS 2.0.1  LAMS 2.0.2

lams_tool: The tool version for noticeboard, chat, scribe are now  20070315. Started change the classpath entry to the format "lams-tool-blah.jar", not "./lams-tool-blah.jar" - new installations will get it without "./" but upgraded versions from 2.0.2 will get a mixture of the two formats. Given that this change just makes the classpaths in the Manifest files shorter, it is not an essential change if upgrading a server.

lams_tool_nb/db/sql/updatescripts/updateTo20070315.sql
lams_tool_chat/db/sql/updatescripts/updateTo20070315.sql
lams_tool_scribe/db/sql/updatescripts/updateTo20070315.sql
update lams_tool set tool_version=20070315 where tool_signature='lanb11';
update lams_tool set tool_version=20070315 where tool_signature='lachat11';
update lams_tool set tool_version=20070315 where tool_signature='lascrb11';
update lams_configuration set config_value='2.0.2' where config_key='Version';
update lams_configuration set config_value='2.0.2.200703270000' where config_key='AuthoringClientVersion';
update lams_configuration set config_value='2.0.2.200703270000' where config_key='MonitorClientVersion';
update lams_configuration set config_value='2.0.2.200703270000' where config_key='LearnerClientVersion';
update lams_configuration set config_value='2.0.2.200703270000' where config_key='ServerVersionNumber';
update lams_configuration set config_value='2007-03-08' where config_key='DictionaryDateCreated';

From LAMS 2.0.2  LAMS 2.0.3

javac -cp "commons-logging.jar:hibernate3.jar:mysql-connector-java-3.1.12-bin.jar:." UpdateLAMS202Chat.java
java -cp "commons-logging.jar:hibernate3.jar:mysql-connector-java-3.1.12-bin.jar:." UpdateLAMS202Chat conference.localhost
update lams_configuration set config_value='2.0.3' where config_key='Version';
update lams_configuration set config_value='2.0.3.200706040000' where config_key='AuthoringClientVersion';
update lams_configuration set config_value='2.0.3.200706040000' where config_key='MonitorClientVersion';
update lams_configuration set config_value='2.0.3.200706040000' where config_key='LearnerClientVersion';
update lams_configuration set config_value='2.0.3.200706040000' where config_key='ServerVersionNumber';
update lams_configuration set config_value='2007-05-24' where config_key='DictionaryDateCreated';

From LAMS 2.0.3 to 2.0.4

We found out after the Windows 2.0.3 upgrader was released that we missed the following code from the editonthefly script. So it will go out in a 2.0.4 release.

INSERT INTO lams_system_tool (system_tool_id, learning_activity_type_id, tool_display_name, description,
learner_url, learner_preview_url, learner_progress_url, export_pfolio_learner_url,
export_pfolio_class_url, monitor_url, contribute_url, create_date_time)
VALUES (5, 9, 'System Gate', 'Gate: Opens under system control.',
'learning/gate.do?method=knockGate', 'learning/gate.do?method=knockGate', null, null,
'monitoring/gateExportPortfolio?mode=teacher', 'monitoring/gate.do?method=viewGate',
'monitoring/gate.do?method=viewGate', now()
);

From LAMS 2.0.3/2.0.4 to 2.0.6

In the ldap2_0_4 branch:

Jar/War replacements:
lams_admin, lams_central, lams_common, lams_monitoring

From LAMS 2.0.4 to 2.1 Beta

From 2.1 Beta to 2.1 RC1

From 2.1 RC1 to 2.1

From 2.1 to 2.1.1

Changes to the database no longer need to be recorded here after 2.1. The dbupdates directory in lams.jar and each tool's jar should be considered the authoritative list of database changes - autopatch will execute these as needed.

This page should still be used to record any changes to configuration files such as log4j.xml, etc.

Before doing the 2.1.1 Release, we will need to add the Google Maps key entry to the LAMS Configuration page.

From 2.1.1 to 2.2