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.
For the 2.1 updatersThis copies adds any exisitng non defualt tool contexts from the database to the web.xmls of central monitoring and learning. It also updates the application.xml if the tool web project is not listed
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
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
[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
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
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
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 hideToolAlso, added a tool update script path, which defaults to "${build.deploy}/sql/updateTo${tool.version}.sqlThese 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 dbTODO: update db and jar and war files if tool exists, but is not the newest version
Skeleton for a new ToolDBUpdater classIt 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
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.
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.
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.
