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
LDEV-1146: Increase login field length to 255. Also increased the workspace folder name to 255 as found that it wasn't long enough for a user with two very long names, while testing the login field changes.
LDEV-1146: Increase login field length to 255Had to change login field edit box to take longer length, so made most of the fields wider (there was plenty of room on the page).
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
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 fixedmy bad
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
Updated author validation on read-only activities and transitions in Edit-on-the-Fly mode. Read only field is set when activity is attempted (ProgressEngine).
