Recommendation Tracker Code

Added null check to prevent NPE when user quits out of login dialog.

Added property change listener on launching Compliance Check editor from list view to mark data as changed. Fix for bug 2791816.
Added cancel option in addition to save and exit options in dialog that pops up when exiting the application and there are unsaved changes. The cancel option lets the user return to the RT. Fix for bug 2758920.

Backed out of change that allowed users to add a compliance check to multiple rules.
Added a new button on the rule dialog compliance check content panel that pops up a dialog that allows user to pick a file that is already used in another compliance check.
This is the second attempt to close feature request 2492249.

Changed text on Browse button to Import and added tooltip to alert user that the files are copied into the RT, not just referenced.

Added instruction in the README about running the create.rtversion.sql script on all updates.
Added creation of the version table to create.rtserver.sql script.
Added inserting the version into the rtversion table. (Note, this should be updated at every release).

Removed date from equals comparison. major, minor, and build are sufficient.

Added missing jar refs. Bug 2786476

Added comparison of build version stored in the database with build version from version.info.properties.
If the versions are not equal and the version.devel property is false, the user will be presented an error message when syncing.
Developers can set the version.devel=true to subvert the check.
A new database script, create.rtversion.sql will need to be updated and run for each release.
Users will see appropriate message if the the client version is newer, older, or if there is no rtversion table in the database.

Feature request #2782819

Added ant task to ensure the all releases have the devel flag set to false.

Added devel flag