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

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. … 2 more files in changeset.
Updated address of FSF in copyright statement

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

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

  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.

  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

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

    • -19
    • +21
    ./java/org/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. … 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.

  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 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.

  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

configuration for tool deployment

Parent class for deploy configurations. common attributes dbUsername, dbPassword, dbDriverClass and dbDriverUrl is shared with child classes.

Main class for tool Deployment. the configurations are stored in DeployToolConfig instead of DeployConfig.

Functions similar to the previous CreatePackageTask. This will generate the deploy properties (xml format) for the toold eployment

CreatePackageTask is now the parent class for creating tool/library packages. It follows the same logic as the original CreatePackageTask, just the some commonality between library and tool package task is extracted

Changed default values to something more standard than Chris' values.