Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-1916 adding autopatch to tools, including db_version_insert.sql script to tool deployer

  1. … 71 more files in changeset.
Small change to tool deployer uncommitted in lams_build jar

LI-161: Replacing / in windows paths to \ to make all the paths consistent.

  1. … 1 more file in changeset.
LI-161: Generate special version of deploy.xml for tools that has a generic parameter in the place of the drive paths. This is turned on in common.properties (generate for installer) in lams_build. Only use this option if you are writing an installer/updater.

  1. … 1 more file in changeset.
LI-161: Generate special version of deploy.xml for tools that has a generic parameter in the place of the drive paths. This is turned on in common.properties (generate for installer) in lams_build. Only use this option if you are writing an installer/updater.

  1. … 21 more files in changeset.
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

  1. … 2 more files in changeset.
lams-tool-deploy.jar has RemoveModuleFromApplicationXML class in it now

[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

  1. … 2 more files in changeset.
Small change to tool deployer to correct version check bug

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. … 4 more files in changeset.
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

  1. … 11 more files in changeset.
lams-tool_deploy generates a tool_version entry for a tool's deploy.xml

  1. … 3 more files in changeset.
Added styling images to export portfolio. This required making lams-central.war an expanded war and adding the lams directory to the configuration file so that the css and image files could be copied using a file copy rather than using http (for performance).

  1. … 6 more files in changeset.
Tool deployment utility has been changed to update the context path and class path when the tool is deployed.

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. … 20 more files in changeset.
Updated Tool Deployer so that that parallel activities, installed using the tool deployer, can also be I18N.

  1. … 6 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. … 4 more files in changeset.
Updated mysql-connector, to go with MySQL 5.0

    • binary
    ./mysql-connector-java-3.1.12-bin.jar
    • binary
    ./mysql-connector-java-3.1.7-bin.jar
  1. … 2 more files 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. … 19 more files in changeset.
*** empty log message ***

If the lams_tool record doesn't exist, doesn't try to delete the lams_blah table entries or the tool's own tables.

Setup tool_deploy so that it can be built and loaded into lams_build project, the properties file generated from a build script and the deployment run from a built script. This was done to make a usuable development tool deploy task as well as make it easier to build the deployment package.

    • binary
    ./commons-collections.jar
    • binary
    ./commons-configuration-1.1.jar
    • binary
    ./commons-dbutils-1.0.jar
    • binary
    ./commons-io-1.0.jar
    • binary
    ./commons-lang-2.0.jar
    • binary
    ./commons-logging.jar
    • binary
    ./lams-tool-deploy.jar
    • binary
    ./mysql-connector-java-3.1.7-bin.jar
  1. … 4 more files in changeset.