Removed the "is this tool on the classpath" hack. Now it will throw a ToolException if a tool can't be fine. This will break one of our junit tests but the test will have to be skipped for the moment or rewritten to use a known set of tools.
Commented out the "in progress" tools from the build. They can now be deployed separately, and temporarily removing them from the build will stop them being deployed on Shaun.
Commented out the "in progress" tools from the build. They can now be deployed separately, and temporarily removing them from the build will stop them being deployed on Shaun.
Tool deployment utility has been changed to update the context path and class path when the tool is deployed. Conf versions of web-settings and manifest files modified to suit and the main tool context application file moved so that only the tool's have a context file classpath of /org/lamsfoundation/lams/tool.
Tool deployment utility has been changed to update the context path and class path when the tool is deployed. Build file changed to match and the main tool context application file moved so that only the tool's have a context file classpath of /org/lamsfoundation/lams/tool.
Tool deployment utility has been changed to update the context path and class path when the tool is deployed. Build file changed to match and the main tool context application file moved so that only the tool's have a context file classpath of /org/lamsfoundation/lams/tool.