LI-167 check if mysql test works on a non-default mysql portupdated backup.java to use the mysql host and port in the mysqldump command so it will work for a non-default mysql port
LI-161 - Fixing so a custom DEFAULT_DIR does not break the tool deployerLI-167 Check if mysql works for a non-default portupdater is now changed to not prompt user for mysql port, it is retrieved either from lams.properties or the stored lams.properties instead
Un-commenting the script that updates the lams versions. This was going to be handled by autopatch, but that would mean that the server version numbers would not be updated for a normal build
LI-167 Check if mysql test works for a non-default mysql portthe problem here was not with jdbc but instead with shell, the SQL_URL's '&' character was getting munged by shell, so escaping it here did the trick
LI-167 Check if mysql test works for a non-default mysql portthe problem here was not with jdbc but instead with shell, the SQL_URL's '&' character was getting munged by shell, so escaping it here did the trick
LI-170 Autopatch now takes care of db updates, so alot of the old ant update task have now been commentedLI-171 New tools added to ant build to use the tool deployerLI-172 application.xml updated to include new builds
LI-171 - Add new tools to the updater for 2.2As of 2.2, we only need to use the tool deployer to add new tools, autopatch will handle any updaters thereafter
LI-135 Configurations were being overwritten by the updater, so people's sysadmin passwords and serverurls were unsuspectinly being changed, commenting out these updates in the setLamsConfiguration should do the trick.For 2.1 (Replaces existing 2.1 unix updater)