lams-github

Clone Tools

Stats

Commits this week: 0
Total Committers: 50
Last Commit:
Commits this week: 0

Lines of code count not available

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
Wednesday 14 Feb 2007
1:46 pm

lfoxton

Added option to hide the tool in deploy.xml, hideTool (boolean), now to hide a tool (for instance scribe), you can put a flag in the tool's build.properties hideTool

Also, added a tool update script path, which defaults to "${build.deploy}/sql/updateTo${tool.version}.sql

These will be generated when you do create-deploy-tool ant task

Options
    • -0
    • +11
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployConfig.java
    • -2
    • +52
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployToolConfig.java
    • -0
    • +1
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/ToolDBUpdater.java
12:28 pm

jliew

make reading user.changePassword more robust

Options
    • -2
    • +4
    /lams_central/src/java/org/lamsfoundation/lams/web/IndexAction.java
12:28 pm

jliew

added changePassword=false to default/minimal constructors

Options
    • -0
    • +2
    /lams_common/src/java/org/lamsfoundation/lams/usermanagement/User.java
12:27 pm

jliew

fix mistake where change_password had 'not-null=true'

Options
    • -2
    • +0
    /lams_common/conf/hibernate/mappings/org/lamsfoundation/lams/usermanagement/User.hbm.xml
11:46 am

lfoxton

Now the deploy-tool update Copies jars and wars and language files and updates the lams_tool table with the tool_version, the only thing left to do is allow for an update script to be written by a tool developer

Options
    • -11
    • +37
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/Deploy.java
    • -2
    • +43
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/ToolDBUpdater.java
11:41 am

mseaton

updated lams translator list (welsh) for about lams dialog

Options
    • binary
    /lams_central/src/flash/lams_authoring.fla
11:23 am

jliew

add spinning 'loading.gif' when user imports

Options
    • -2
    • +18
    /lams_admin/web/import/importv1.jsp
    • -16
    • +28
    /lams_admin/web/import/importv1contents.jsp
11:23 am

jliew

send extra 'no. of sessions' attribute to jsp, doesn't cause javascript warnings like before

Options
    • -1
    • +8
    /lams_admin/src/java/org/lamsfoundation/lams/admin/web/action/ImportV1ContentsAction.java
11:22 am

jliew

handle v1 user with no orgrights without causing null exception, even though a v1 user should always have at least 1 orgright

Options
    • -3
    • +5
    /lams_admin/src/java/org/lamsfoundation/lams/admin/web/action/ImportV1ContentsSaveAction.java
11:19 am

mseaton

updated lams translator list (welsh) for about lams dialog

Options
    • binary
    /lams_central/src/flash/lams_authoring.fla
    • binary
    /lams_central/web/lams_authoring.swf
    • binary
    /lams_central/web/lams_authoring_library.swf
11:07 am

mseaton

fixed monitor - remove lesson problem ldev-1096

Options
    • binary
    /lams_monitoring/web/lams_monitoring.swf
    • binary
    /lams_monitoring/web/lams_monitoring_library.swf
10:33 am

lfoxton

Tool-deployer upgrade, checks the db for tool_signature and tool_version, stops if current tool is up to date, installs entire tool if the signature is not present in the db

TODO: update db and jar and war files if tool exists, but is not the newest version

Options
    • binary
    /lams_build/deploy-tool/lib/lams-tool-deploy.jar
    • -0
    • +42
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/Deploy.java
    • -0
    • +16
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployConfig.java
    • -4
    • +5
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployToolConfig.java
    • -20
    • +90
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/ToolDBUpdater.java
10:05 am

lfoxton

Fixed problem which arose when deploy-tools is called. The generated deploy.xml was pointing to the wrong sql scripts, the problem originated in the build.xml of the tools, now fixed

my bad

Options
    • binary
    /lams_build/deploy-tool/lib/lams-tool-deploy.jar
    • -2
    • +2
    /lams_tool_example/build.xml
    • -2
    • +2
    /lams_tool_forum/build.xml
    • -2
    • +2
    /lams_tool_lamc/build.xml
    • -2
    • +2
    /lams_tool_laqa/build.xml
    • -4
    • +4
    /lams_tool_larsrc/build.xml
    • -2
    • +2
    /lams_tool_nb/build.xml
    • -2
    • +2
    /lams_tool_notebook/build.xml
    • -2
    • +2
    /lams_tool_sbmt/build.xml
    • -2
    • +2
    /lams_tool_scribe/build.xml
    • -4
    • +4
    /lams_tool_survey/build.xml
    • -2
    • +2
    /lams_tool_vote/build.xml
7:42 am

lfoxton

Skeleton for a new ToolDBUpdater class

It will:

* Check if the tool exists in the db

* Check if the tool to be installed is newer than the current

* Update the db with the current tool information

Options
    • -0
    • +93
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/ToolDBUpdater.java
Tuesday 13 Feb 2007
2:26 pm

lfoxton

Changing the tool's build.xml to copy the .jar and .war to the build/deploy folder, and updates the deploy.xml to point to these files

Options
    • -2
    • +9
    /lams_tool_example/build.xml
    • -1
    • +8
    /lams_tool_forum/build.xml
    • -1
    • +8
    /lams_tool_lamc/build.xml
    • -1
    • +8
    /lams_tool_laqa/build.xml
    • -1
    • +8
    /lams_tool_larsrc/build.xml
    • -1
    • +8
    /lams_tool_nb/build.xml
    • -1
    • +8
    /lams_tool_notebook/build.xml
    • -1
    • +8
    /lams_tool_sbmt/build.xml
    • -1
    • +8
    /lams_tool_scribe/build.xml
    • -1
    • +8
    /lams_tool_survey/build.xml
    • -1
    • +8
    /lams_tool_vote/build.xml
1:42 pm

lfoxton

Changing the tool's build.xml so the create-deploy package copies the .war and .jar files from build/lib to /build.deploy

The deploy.xml is also updated to point to the jar and war in build/deploy

Options
    • -1
    • +8
    /lams_tool_chat/build.xml
1:27 pm

lfoxton

Changing the build.xml of all the tools so the generated deploy.xml points to the sql scripts in the build/deploy/sql folder instead of the db/sql folder

Options
    • -5
    • +5
    /lams_tool_chat/build.xml
    • -6
    • +6
    /lams_tool_example/build.xml
    • -5
    • +5
    /lams_tool_forum/build.xml
    • -5
    • +5
    /lams_tool_lamc/build.xml
    • -5
    • +5
    /lams_tool_laqa/build.xml
    • -5
    • +5
    /lams_tool_larsrc/build.xml
    • -5
    • +5
    /lams_tool_nb/build.xml
    • -5
    • +5
    /lams_tool_notebook/build.xml
    • -5
    • +5
    /lams_tool_sbmt/build.xml
    • -5
    • +5
    /lams_tool_scribe/build.xml
    • -5
    • +5
    /lams_tool_survey/build.xml
    • -5
    • +5
    /lams_tool_vote/build.xml
9:33 am

lfoxton

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -6
    • +6
    /lams_tool_chat/build.xml
9:27 am

lfoxton

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -0
    • +3
    /lams_tool_survey/build.properties
    • -1
    • +10
    /lams_tool_survey/build.xml
    • -1
    • +1
    /lams_tool_survey/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_vote/build.properties
    • -1
    • +10
    /lams_tool_vote/build.xml
    • -1
    • +1
    /lams_tool_vote/db/sql/tool_insert.sql
9:19 am

lfoxton

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -1
    • +4
    /lams_tool_example/build.properties
    • -0
    • +3
    /lams_tool_larsrc/build.properties
    • -1
    • +10
    /lams_tool_larsrc/build.xml
    • -1
    • +1
    /lams_tool_larsrc/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_nb/build.properties
    • -1
    • +10
    /lams_tool_nb/build.xml
    • -1
    • +1
    /lams_tool_nb/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_notebook/build.properties
    • -1
    • +10
    /lams_tool_notebook/build.xml
    • -1
    • +1
    /lams_tool_notebook/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_sbmt/build.properties
    • -1
    • +10
    /lams_tool_sbmt/build.xml
    • -1
    • +1
    /lams_tool_sbmt/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_scribe/build.properties
    • -1
    • +10
    /lams_tool_scribe/build.xml
    • -1
    • +1
    /lams_tool_scribe/db/sql/tool_insert.sql
9:05 am

fmalikoff

LDEV-1144: Two bugs: * The submit is trying to call a javascript function that does not exist. I can't find any code that suggests it ever existed! * The pages are trying to load up a css file that doesn't exist. At least in this case, the file did exist in the past but it was removed.

Removed the onsubmit call and the css reference.

Options
    • -1
    • +0
    /lams_tool_forum/web/common/header.jsp
    • -1
    • +1
    /lams_tool_forum/web/jsps/learning/edit.jsp
    • -1
    • +1
    /lams_tool_forum/web/jsps/learning/reply.jsp
9:01 am

lfoxton

Changes made to all tools, so they should be made in the example tool

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -0
    • +1
    /lams_tool_example/build.xml
    • -1
    • +1
    /lams_tool_example/db/sql/tool_insert.sql
    • -0
    • +4
    /lams_tool_lamc/build.properties
    • -1
    • +10
    /lams_tool_lamc/build.xml
    • -1
    • +1
    /lams_tool_lamc/db/sql/tool_insert.sql
    • -0
    • +3
    /lams_tool_laqa/build.properties
    • -1
    • +10
    /lams_tool_laqa/build.xml
    • -1
    • +1
    /lams_tool_laqa/db/sql/tool_insert.sql
8:53 am

lfoxton

Changes made to all tools, so they should be made in the example tool

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -1
    • +1
    /lams_tool_example/build.properties
    • -1
    • +9
    /lams_tool_example/build.xml
8:48 am

lfoxton

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -0
    • +1
    /lams_tool_chat/build.properties
    • -2
    • +11
    /lams_tool_chat/build.xml
    • -1
    • +1
    /lams_tool_chat/db/sql/tool_insert.sql
8:33 am

lfoxton

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Options
    • -1
    • +1
    /lams_tool_forum/build.properties
    • -2
    • +12
    /lams_tool_forum/build.xml
    • -1
    • +1
    /lams_tool_forum/db/sql/tool_insert.sql
8:28 am

lfoxton

lams-tool_deploy generates a tool_version entry for a tool's deploy.xml

Options
    • binary
    /lams_build/deploy-tool/lib/lams-tool-deploy.jar
    • -0
    • +5
    /lams_tool_deploy/build.xml
    • -1
    • +2
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployConfig.java
    • -1
    • +26
    /lams_tool_deploy/src/java/org/lamsfoundation/lams/tool/deploy/DeployToolConfig.java
Monday 12 Feb 2007
10:01 am

jliew

missing message key (also found in lams_admin's resources)

Options
    • -0
    • +1
    /lams_central/conf/language/ApplicationResources.properties
    • -0
    • +1
    /lams_central/conf/language/ApplicationResources_en_AU.properties
Friday 09 Feb 2007
4:11 pm

fmalikoff

Translation key was wrong for the export button.

Options
    • -1
    • +1
    /lams_tool_survey/web/pages/monitoring/summary.jsp
2:56 pm

fmalikoff

LDEV-1097: Changed the learner progress screen to be a read only version of the learner's progressive results screen.

Options
    • -1
    • +0
    /lams_tool_vote/src/java/org/lamsfoundation/lams/tool/vote/VoteAppConstants.java
    • -160
    • +169
    /lams_tool_vote/src/java/org/lamsfoundation/lams/tool/vote/web/VoteLearningStarterAction.java
    • -7
    • +0
    /lams_tool_vote/web/WEB-INF/struts-config.xml
    • -7
    • +8
    /lams_tool_vote/web/learning/ExitLearning.jsp
    • -183
    • +0
    /lams_tool_vote/web/learning/LearnerRep.jsp
2:05 pm

fmalikoff

LDEV-1142: Change the answer text field to text, so that it can take longer text.

Options
    • -133
    • +132
    /lams_tool_survey/db/model/survey.clay
    • -1
    • +1
    /lams_tool_survey/db/sql/create_lams_tool_survey.sql
    • -1
    • +1
    /lams_tool_survey/db/sql/tool_insert.sql
    • -0
    • +5
    /lams_tool_survey/db/sql/updatescripts/updateTo20070208.sql