lams_tool_deploy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

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

  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

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

  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

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

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

  1. … 1378 more files in changeset.
Update wars either expanded or zipped.

The main tool context application file moved so that only the tool's have a context file classpath of /org/lamsfoundation/lams/tool.

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

    • -0
    • +499
    ./src/java/org/lamsfoundation/lams/tool/deploy/UpdateWarTask.java
Added manifest file to the test war, to test adding the tool jar to the classpath

Implemented the extraction and re-zipping of the war files. Tested with unit tests. Next step to integrate with the deployment script.

Test war used to test removing the nb tool application entry from the web.xml

    • binary
    ./test/file/test-dummy-with-nb.war
Previous check in had two many levels of directories (rar utility strikes again!)

The previous version wasn't a true war - it was actually a jar. This should now be a functioning war.

Implemented remove application context entry.

Improving the insert side of the test.

    • -0
    • +214
    ./test/file/web1EntryInsert.xml
Improving the remove side of the test.

    • -0
    • +214
    ./test/file/web1Entry.xml
    • -0
    • +215
    ./test/file/web3Entry.xml
    • -0
    • +213
    ./test/file/webNoEntry.xml
Made the test harder with a multiline comment.

Made the test harder with a multiline comment.

Test file for the web.xml changes

    • -0
    • +211
    ./test/file/web2.xml
    • -0
    • +212
    ./test/file/web3.xml
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

Test file for the web.xml changes

    • -0
    • +210
    ./test/file/web.xml
Updated copyright statement - only support GPL v 2.0

  1. … 37 more files in changeset.
Updated copyright statement - only support GPL v 2.0

  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. … 6 more files in changeset.
Added the Id keyword for expansion.