Index: win_installer/license.txt
===================================================================
RCS file: /usr/local/cvsroot/win_installer/Attic/license.txt,v
diff -u -r1.8 -r1.9
--- win_installer/license.txt	5 Feb 2007 04:46:59 -0000	1.8
+++ win_installer/license.txt	1 Mar 2007 05:15:25 -0000	1.9
@@ -1,4 +1,4 @@
-LAMS 2.0 is released under the GPL license detailed below.  This package
+LAMS 2.0.1 is released under the GPL license detailed below.  This package
 also includes other libraries/packages, whose respective licenses are
 detailed below.
 
Index: win_installer/readme.txt
===================================================================
RCS file: /usr/local/cvsroot/win_installer/Attic/readme.txt,v
diff -u -r1.2 -r1.3
--- win_installer/readme.txt	5 Dec 2006 03:11:16 -0000	1.2
+++ win_installer/readme.txt	1 Mar 2007 05:15:26 -0000	1.3
@@ -1,7 +1,7 @@
-LAMS 2.0 - Learning Activity Management System
+LAMS 2.0.1.1 - Learning Activity Management System
 ----------------------------------------------
 
-This is a pre-packaged copy of LAMS 2.0 for Windows 2000, XP, or 2003.
+This is a pre-packaged copy of LAMS 2.0.1 for Windows 2000, XP, or 2003.
 For the source code, please see the 'Building LAMS' wiki at 
 
 	http://wiki.lamsfoundation.org/display/lams/Building+LAMS 
@@ -11,14 +11,15 @@
 
 1. Startup and Shutdown
 =======================
-To use LAMS 2.0, first make sure it is started - use the 'Start LAMS' shortcut
+To use LAMS 2.0.1, first make sure it is started - use the 'Start LAMS' shortcut
 in the LAMSv2 Start Menu folder if you're not sure.  MySQL must be running.
 For chat rooms to function, Wildfire must also be running.
 
-While LAMS 2.0 is running, you may access the login page using the 'Access 
+While LAMS 2.0.1 is running, you may access the login page using the 'Access 
 LAMS' short cut in the LAMSv2 Start Menu folder.
 
-To stop LAMS 2.0, use the 'Stop LAMS' shortcut in the LAMSv2 Start Menu folder.
+To stop LAMS 2.0.1, use the 'Stop LAMS' shortcut in the LAMSv2 Start Menu 
+folder.
 
 2. Server Configuration
 =======================
@@ -27,7 +28,7 @@
 
 For server deployments, you will probably want to configure the default JVM 
 memory settings for your server.  In C:\lams\jboss-4.0.2\bin\run.bat (or 
-wherever you installed LAMS 2.0), find the line near the bottom that says
+wherever you installed LAMS 2.0.1), find the line near the bottom that says
 
 	set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
 	
@@ -48,19 +49,19 @@
 
 	http://wiki.lamsfoundation.org/display/lamsdocs/Windows+Installer+Help
 	
-LAMS 2.0 developer-oriented information
+LAMS 2.0.1 developer-oriented information
 
 	http://wiki.lamsfoundation.org/display/lams
 
-LAMS 2.0 help documents
+LAMS 2.0.1 help documents
 
 	http://wiki.lamsfoundation.org/display/lamsdocs
 
 Educational and technical forums for help and discussion
 				
 	http://www.lamscommunity.org
 
-LAMS 2.0 bug tracker			
+LAMS 2.0.1 bug tracker			
 
 	https://bugs.lamsfoundation.org
 
Index: win_installer/src/language-pack.nsi
===================================================================
RCS file: /usr/local/cvsroot/win_installer/src/Attic/language-pack.nsi,v
diff -u -r1.33 -r1.34
Binary files differ
Index: win_installer/src/updater.nsi
===================================================================
RCS file: /usr/local/cvsroot/win_installer/src/Attic/updater.nsi,v
diff -u -r1.1 -r1.2
Binary files differ
Index: win_installer/templates/update-deploy-tools.xml
===================================================================
RCS file: /usr/local/cvsroot/win_installer/templates/Attic/update-deploy-tools.xml,v
diff -u -r1.1 -r1.2
--- win_installer/templates/update-deploy-tools.xml	26 Feb 2007 23:49:35 -0000	1.1
+++ win_installer/templates/update-deploy-tools.xml	1 Mar 2007 05:15:25 -0000	1.2
@@ -28,7 +28,7 @@
 		    <classpath refid="deploy.lib.classpath"/>
 		</taskdef>
 
-		<generateDeployProperties depends="compile" 
+		<generateDeployProperties 
 			mode="production" 
 			outputPath="${build.deploy}"
 			dbPassword="${db.password}"
@@ -61,8 +61,42 @@
 				
 		</generateDeployProperties>
 		
+		<echo>Deploy packaqe for ${signature} created.</echo>
+			
+		<echo>Updating web.xml and MANIFEST.MF for lams-central.war, lams-monitor.war and lams-learning.war.</echo>
+		<java classname="org.lamsfoundation.lams.tool.deploy.UpdateToolContextPath" classpathref="deploy.lib.classpath" fork="true">
+						<arg file="${build.deploy}/deploy.xml" />
+		</java>	
+		
 	</target>
 	
+	<target name="update-application-xml" description="Removes unneccessary modules from application.xml">
+		<path id="deploy.lib.classpath">
+			<fileset dir="${deploy.tool.dir}">
+				<include name="lib/*.jar"/>
+			</fileset>
+		</path>
+		
+		<echo>Updating application.xml</echo>
+		
+		<java classname="org.lamsfoundation.lams.tool.deploy.RemoveModuleFromApplicationXmlTask" classpathref="deploy.lib.classpath" fork="true">
+			<arg value="${jboss.deploy}" />
+		</java>
+		
+	</target>
+	
+	
+	<target name="explode-wars" description="explodes lams_learning.war and lams-monitoring.war">
+		<rename src="${jboss.deploy}/lams-learning.war" dest= "${jboss.deploy}/lams-learning.war.bak" />
+		<rename src="${jboss.deploy}/lams-monitoring.war" dest= "${jboss.deploy}/lams-monitoring.war.bak" />
+		
+		<mkdir dir="${jboss.deploy}/lams-learning.war/"/>
+		<mkdir dir="${jboss.deploy}/lams-monitoring.war/"/>
+		
+		<unwar src="${jboss.deploy}/lams-learning.war" dest="${jboss.deploy}/lams-learning.war" />
+		<unwar src="${jboss.deploy}/lams-monitoring.war" dest="${jboss.deploy}/lams-monitoring.war" />
+	</target>
+	
 	<target name="deploy-tool" description="runs the tool deployer for a given tool">
 		<path id="deploy.lib.classpath">
 			<fileset dir="${deploy.tool.dir}">
@@ -89,6 +123,7 @@
 			<transaction src="${temp}/lams/sql/alter_201_system_tool_user_workspace.sql" />
 			<transaction src="${temp}/lams/sql/alter_201_theme.sql" />
 			<transaction src="${temp}/lams/sql/alter_201_tool.sql" />
+			<transaction src="${temp}/lams/sql/alter_201_ext.sql" />
 		</sql>
 	</target>
 	
Index: win_installer/templates/update_lams_configuration.sql
===================================================================
RCS file: /usr/local/cvsroot/win_installer/templates/Attic/update_lams_configuration.sql,v
diff -u -r1.4 -r1.5
--- win_installer/templates/update_lams_configuration.sql	8 Jan 2007 22:50:57 -0000	1.4
+++ win_installer/templates/update_lams_configuration.sql	1 Mar 2007 05:15:25 -0000	1.5
@@ -11,4 +11,9 @@
 update lams_configuration set config_value='@WILDFIRE_USER@' where config_key='XmppAdmin';
 update lams_configuration set config_value='@WILDFIRE_PASS@' where config_key='XmppPassword';
 update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where user_id=1;
-update lams_user set locale_id=(select locale_id from lams_supported_locale where language_iso_code=(SELECT SUBSTRING_INDEX('@LOCALE@', '_', 1)) and country_iso_code=(SELECT SUBSTRING_INDEX('@LOCALE@', '_', -1))) where user_id=1;
\ No newline at end of file
+update lams_user set locale_id=(select locale_id from lams_supported_locale where language_iso_code=(SELECT SUBSTRING_INDEX('@LOCALE@', '_', 1)) and country_iso_code=(SELECT SUBSTRING_INDEX('@LOCALE@', '_', -1))) where user_id=1;
+update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where login='test';
+update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where login='test1';
+update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where login='test2';
+update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where login='test3';
+update lams_user set login='@LAMS_USER@', password=sha1('@LAMS_PASS@') where login='test4';
\ No newline at end of file