Release Notes: Kwatee now uses an H2 embedded database by default. A new command line deployer enables deployment to multiple servers within a datacenter in command line mode. There were also user interface improvements and many other enhancements.
Release Notes: Fixes the following bugs: Windows offline installer deployment actions are now executed; removal of a legacy limitation on deployable number of servers per release; empty directories in archives are now supported.
Release Notes: This release fixes the "missing agent" issue with deployments on Solaris SPARC.
Release Notes: This release fixed a problem where a newly created Amazon EC2 pool generated a 500 error. An issue with zip files containing a single entry showing up as empty was fixed. A problem with system variable override not working properly in frozen deployments was fixed.
Release Notes: This release fixes a bug in upgrading MySQL schema (apologies to MySQL users).
Release Notes: Increased variable name size. Dots accepted in variable names. Bugfixes (offline deployment actions not executed; could not upload an overlay at the root level of a package; pre-setup script not executed unless a post-setup script was defined; and some kwatee variables had incorrect values after a deployment freeze.)
Release Notes: This release no longer performs automatic integrity checks before stopping operation. It fixes "environment variable server/package qualifiers lost in import" and "environment bundle import fails in 'upload' mode"
Release Notes: A major issue with zip archives which could not be uploaded is resolved. A cosmetic issue with overlays showing at the root of archives is resolved. kwateelib (and therefore update.py) can now update archives even when kwatee is not running on localhost. Be sure to use the latest kwateelib task in your deployment automation.
Release Notes: This release fixes an archive update failure via ant/maven when the kwatee URL was not on localhost.
Release Notes: This release adds support for regions in EC2 server pools. It fixes an occasional maven task "bad parameter" error and a serious bug that caused all logins to fail after an attempt with an unknown user was made.