--------------------------------------
| Migration instructions from TaskDB |
--------------------------------------

TaskDB is the predecessor program of improve!
You can migrate the data base from TaskDB to improve! using the following
instructions.

Important:

- The password hashing has changed from TaskDB to improve! The migration
  script resets all password to 'password'. Users should change their
  passwords immediately after migration!

- Also, improve! contains new features not covered by TaskDB. After the
  migration you should reconfigure your users and projects to meet your needs.
  For example, the master administrator has disappeared. Instead, you can
  create issue reporters and guests now, and the manager, developer, and
  reporter permissions are assigned on a per-project basis.

Migration instructions:

- Stop both the mysqld and the JSP/Servlet container.

- Backup your data base to return to TaskDB if anything fails.

- Verify that you use Java 2 Standard Edition 1.4.2 or higher.

- Verify that your JSP/Servlet container supports the Servlet API 2.4 or
  higher and the JSP API 2.0 or higher, e.g. Tomcat 5.0.

- Verify that you use MySQL 4.1 or higher.

- Execute the migration script src/sql/migrate-from-taskdb.sql, e.g.:
  mysql improve <src/sql/migrate-from-taskdb.sql

- Copy the MySQL driver, as well as lib/j2ee/activation.jar,
  lib/j2ee/mailapi.jar, lib/j2ee/smtp.jar, and lib/j2ee/jta.jar
  (if not provided by the JSP/Servlet Container) into the external library
  folder of the Container.
  For Tomcat, this is common/lib, for Resin, this is lib.

- Configure the J2EE DataSource (for data base connections) and Mail Session
  (for email notifications). The DataSource must be available under JNDI key
  'jdbc/DataSource' and the Mail Session under key 'mail/Session'. You can
  find Container configuration examples in the conf/tomcat-example and
  conf/resin-example folders that only need minimal adjustments for your
  installation.

- Start both the mysqld and the JSP/Servlet container.
