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).
Changing the tool's build.xml so the create-deploy package copies the .war and .jar files from build/lib to /build.deployThe deploy.xml is also updated to point to the jar and war in build/deploy
Changing the build.xml of all the tools so the generated deploy.xml points to the sql scripts in the build/deploy/sql folder instead of the db/sql folder
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
LDEV-1144: Two bugs:* The submit is trying to call a javascript function that does not exist. I can't find any code that suggests it ever existed!* The pages are trying to load up a css file that doesn't exist. At least in this case, the file did exist in the past but it was removed.Removed the onsubmit call and the css reference.
Changes made to all tools, so they should be made in the example toolChanges to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
Changes made to all tools, so they should be made in the example toolChanges to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version
made authoring (edit-on-fly) popup out of monitor (temp.) + authoring changes for edit mode (loading design to edit on startup) + canvas view changes (lesson name lip) + backend java changes for setting up edit locks for LD
(This was changed in all the other tools, so should also be changed for the example tool) Changing build.xml "deploy-tool" target to separate the compilation and deploy processess. This will be used later for debian packaging