lams-github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tool deployer now finds and runs the update script

All tools their update script to the deploy dir when the creat-tool-package task is called

Checks the minimum compatible version of the tool from deploy.xml with the existing version in the lams_configuration table, failes if the tool is not compatible

Changed the tool_version to 20070214 for qa, mc, vote and nb

Adds a min server version number to deploy.xml, to check if the tool to be installed is compatible

adding a minServerversionNumber field to deploy.xml when create-tool-package is called for all tools

Changing the minimum server version number in all the tool's build.xml to 2.0.200612051427, (lams-2.0)

added an entry to all the tool's build.xml for minServerVersionNumber to be put in the deploy.xml

Added in a flag hideTool in all the tool's build.properties

  1. … 7 more files in changeset.
Closes [LI-53] and nearly closes [LI-50] There is now an option in every tool's build.xml called hideTool, if set to true, the tool's valid flag will be set to 1 or 0 if false when the tool is deployed

LDEV-1146: Increase login field length to 255. Changed fields on screen to match the fields in the user creation screen in admin.

    • -15
    • +15
    /lams_central/web/editprofile.jsp
LDEV-1146: Increase login field length to 255. Also fixed up fullname field to better accomodate people will long first names and surnames

    • -76
    • +76
    /lams_tool_laqa/db/model/lams_tool_qa.clay
    • -157
    • +157
    /lams_tool_nb/db/model/lams_tool_nb.clay
    • -2
    • +2
    /lams_tool_nb/db/sql/create_lams_tool_nb.sql
    • -2
    • +2
    /lams_tool_nb/db/sql/init_lams_tool_nb.sql
    • -75
    • +75
    /lams_tool_vote/db/model/lams_tool_vote.clay
    • -2
    • +2
    /lams_tool_vote/db/sql/create_lams_tool_vote.sql
LDEV-1146: Increase login field length to 255.

    • -90
    • +90
    /lams_tool_lamc/db/model/lams_tool_mc.clay
LDEV-1146: Increase login field length to 255. Also increased the workspace folder name to 255 as found that it wasn't long enough for a user with two very long names, while testing the login field changes.

    • -2
    • +2
    /lams_common/db/sql/create_lams_11_tables.sql
    • -1
    • +1
    /lams_common/db/sql/insert_windows_config_data.sql
    • -0
    • +22
    /lams_common/db/sql/updatescripts/alter_201_system_tool_user_workspace.sql
LDEV-1146: Increase login field length to 255 Had to change login field edit box to take longer length, so made most of the fields wider (there was plenty of room on the page).

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

make reading user.changePassword more robust

added changePassword=false to default/minimal constructors

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

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

updated lams translator list (welsh) for about lams dialog

    • binary
    /lams_central/src/flash/lams_authoring.fla
add spinning 'loading.gif' when user imports

    • -2
    • +18
    /lams_admin/web/import/importv1.jsp
    • -16
    • +28
    /lams_admin/web/import/importv1contents.jsp
send extra 'no. of sessions' attribute to jsp, doesn't cause javascript warnings like before

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

updated lams translator list (welsh) for about lams dialog

    • binary
    /lams_central/src/flash/lams_authoring.fla
    • binary
    /lams_central/web/lams_authoring.swf
    • binary
    /lams_central/web/lams_authoring_library.swf
fixed monitor - remove lesson problem ldev-1096

    • binary
    /lams_monitoring/web/lams_monitoring.swf
    • binary
    /lams_monitoring/web/lams_monitoring_library.swf
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

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

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

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