Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Change to tool deployer so that scribe is hidden correctly when it is updated. Ie its valid flag is set in lams_tool and disabled in lams_learning_library

    • -2
    • +2
    ./lamsfoundation/lams/tool/deploy/Deploy.java
  1. … 1 more file in changeset.
Added functionality to be used for the installer/updater, it now correctly updates teh web.xml and manifests in the lams_learning, lams-central and lams-monitoring wars. it also updates the application.xml

    • -0
    • +66
    ./lamsfoundation/lams/tool/deploy/RemoveModuleFromApplicationXmlTask.java
[LI-57] Added in an extra class to deploy UpdateToolContextPath.jave, if you call its main method with the path to a tool's deploy.xml, it will update the manifests and web.xmls for lams-central.war, lams-learning.war and lams-monitoring.war instead of replacing them with new ones

    • -0
    • +105
    ./lamsfoundation/lams/tool/deploy/UpdateToolContextPath.java
  1. … 1 more file in changeset.
Small change to correct a bug that gave the wrong value for the server version in the database

Tool deployer now finds and runs the update script

    • -1
    • +8
    ./lamsfoundation/lams/tool/deploy/Deploy.java
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

    • -9
    • +1
    ./lamsfoundation/lams/tool/deploy/Deploy.java
Adds a min server version number to deploy.xml, to check if the tool to be installed is compatible

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

    • -13
    • +34
    ./lamsfoundation/lams/tool/deploy/Deploy.java
  1. … 2 more files in changeset.
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

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

    • -11
    • +37
    ./lamsfoundation/lams/tool/deploy/Deploy.java
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

    • -0
    • +42
    ./lamsfoundation/lams/tool/deploy/Deploy.java
  1. … 1 more file in changeset.
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

    • -0
    • +93
    ./lamsfoundation/lams/tool/deploy/ToolDBUpdater.java
lams-tool_deploy generates a tool_version entry for a tool's deploy.xml

  1. … 2 more files in changeset.
Updated address of FSF in copyright statement

    • -1
    • +1
    ./lamsfoundation/lams/tool/deploy/DBTask.java
    • -1
    • +1
    ./lamsfoundation/lams/tool/deploy/Deploy.java
  1. … 1378 more files in changeset.
Update wars either expanded or zipped.

Implemented the addition of a tool's jar to the classpath.

    • -7
    • +21
    ./lamsfoundation/lams/tool/deploy/Deploy.java
    • -0
    • +94
    ./lamsfoundation/lams/tool/deploy/InsertToolContextClasspathTask.java
    • -0
    • +89
    ./lamsfoundation/lams/tool/deploy/RemoveToolContextClasspathTask.java
    • -0
    • +499
    ./lamsfoundation/lams/tool/deploy/UpdateWarTask.java
  1. … 1 more file in changeset.
Implemented the extraction and re-zipping of the war files. Tested with unit tests. Next step to integrate with the deployment script.

  1. … 1 more file in changeset.
Implemented remove application context entry.

    • -0
    • +77
    ./lamsfoundation/lams/tool/deploy/InsertContextWebXmlTask.java
    • -0
    • +78
    ./lamsfoundation/lams/tool/deploy/RemoveContextWebXmlTask.java
  1. … 1 more file in changeset.
Tweak to try to stop it readding an existing context file.

Added a tool's applicationContext entry to the web.xml files for monitoring, learning and central

    • -0
    • +326
    ./lamsfoundation/lams/tool/deploy/UpdateWebXmlTask.java
  1. … 1 more file in changeset.
Updated copyright statement - only support GPL v 2.0

    • -19
    • +22
    ./lamsfoundation/lams/tool/deploy/DBTask.java
    • -19
    • +22
    ./lamsfoundation/lams/tool/deploy/Deploy.java
    • -19
    • +21
    ./lamsfoundation/lams/tool/deploy/RemoveWebAppFromApplicationXmlTask.java
    • -19
    • +21
    ./lamsfoundation/lams/tool/deploy/Task.java
  1. … 172 more files in changeset.
Completed linking of a language file to a complex activity. The last check in of code was missing setting the language file in the database - it only copied the file.

On doing this second part, I found that I hadn't passed data around in the same manner as Chris originally designed. So I removed the Maps returned by the tasks and went over to Chris' way of just calling the tasks to get any necessary cross-task information.

    • -1
    • +1
    ./lamsfoundation/lams/tool/deploy/DBTask.java
    • -4
    • +1
    ./lamsfoundation/lams/tool/deploy/Task.java
  1. … 6 more files in changeset.
Updated Tool Deployer so that that parallel activities, installed using the tool deployer, can also be I18N.

Also added the Id keyword for expansion.

    • -2
    • +3
    ./lamsfoundation/lams/tool/deploy/DBTask.java
    • -1
    • +1
    ./lamsfoundation/lams/tool/deploy/Deploy.java
    • -2
    • +6
    ./lamsfoundation/lams/tool/deploy/Task.java
  1. … 11 more files in changeset.
Added greater flexibility to the language files for the tool deployment - the deployment configuration now specfies the package into which the file(s) shoul be placed. For tools this may be their normal package, or a tool signature directory. For non-tool activities this will be a artificial name.

    • -1
    • +1
    ./lamsfoundation/lams/tool/deploy/Deploy.java
  1. … 1 more file in changeset.
Copies specified language files from tool directories to the lams-dictionary.jar in the ear. Added a fileset to the ant tag - couldn't do it as nicely as I would have wanted as I couldn't get nested tags working.

    • -4
    • +3
    ./lamsfoundation/lams/tool/deploy/DBTask.java
    • -0
    • +13
    ./lamsfoundation/lams/tool/deploy/Deploy.java
    • -0
    • +91
    ./lamsfoundation/lams/tool/deploy/DeployLanguageFilesTask.java
  1. … 5 more files in changeset.
*** empty log message ***

  1. … 8 more files in changeset.
Classes specific for deployment of a library activity that contains more than one tool activity

sample tool deploy properties file

    • -0
    • +20
    ./lamsfoundation/lams/tool/deploy/templateDeployTool.xml
configuration for tool deployment

    • -0
    • +443
    ./lamsfoundation/lams/tool/deploy/DeployToolConfig.java
Parent class for deploy configurations. common attributes dbUsername, dbPassword, dbDriverClass and dbDriverUrl is shared with child classes.

    • -575
    • +185
    ./lamsfoundation/lams/tool/deploy/DeployConfig.java