Current Status - Ganymede 1.0.12 - March 1, 2004

Ganymede 1.0.12 has been put up for download.

This is a rather long delayed maintenance release of the Ganymede directory management software. The biggest bug fixes relate to infrequently encountered (by us) stability issues in the Ganymede server, particularly the Ganymede scheduler's exception handling.

The biggest change, though, involves the means by which Ganymede clients communicate with the Ganymede server. Ganymede clients can now function perfectly well when run on systems with tightly locked-down system firewalls. Previously, the Ganymede server sent messages to the client during the login process and to notify the client of build status changes and administrative disconnects. In 1.0.12, the Ganymede client includes a thread which polls the server for these asynchronous messages. Since the client initiates these communications, a personal firewall on the client system will not impede the system's functioning.

There were some changes to Ganymede object class method signatures, so custom code may need to be very slightly revised to work with this release. See the CHANGES file for details. As with every release, we recommend you build and test your custom code against the code in this distribution before putting this release into production.

Speaking of which.

This is the last release of Ganymede. The next release of this software will carry a new name, a new class structure, and a new, Ant-based build process. This is to honor a commitment we made to the NetIQ corporation to step out of the way of their Ganymede trademark, and to reduce the maintenance burden for the existing code base.

The next iteration of this software will definitively not be drop-in compatible with your existing custom plug-in software classes. At a minimum, you will need to change your import and subclass definitions to reference the package structure that we will be introducing in the next release. We do not intend at this time to significantly change the plug-in code structure, but we remain interest in evolving the Ganymede data model towards support for containment and type hierarchy. While this work may surface in the first release of Ganymede under its new name, we have not made this decision yet.

1. [CLIENT] Properly update StringSelector count display on manual item entry
2. [SERVER] Fixed regression in object event label display
3. [SERVER] Fixed exception vulnerability in admin console, scheduler code
4. [SERVER] Turned off extraneous debug output from XML processing logic
5. [SERVER] Removed 1.4-only StringBuffer method usage from DBEditObject.java
6. [SERVER SCRIPTS] Fixed RMIGC definition in runServer for ksh
7. [SERVER] Preparations for logging to PostGreSQL
8. [SERVER, CLIENT] Reworked client and server to support direct login
9. [CLIENT] Improvements to text messages in dialogs
10. [CLIENT/CONSOLE/SERVER] Reworked RMI API to be system firewall transparent
11. [CLIENT] Fixed gclient.getObjectHandle()
12. [SERVER] Improved namespace conflict message
13. [SERVER] Cleaned up DBObject.getTypeName()/getTypeDesc()
14. [CLIENT] Added row count indicator to query window
15. [CLIENT] Various tweaks for better behavior under JDK 1.5 beta

Help improve Ganymede! We need your comments on the software and documentation as it stands today. Don't be shy.. if it doesn't work, tell us. If it does work, tell us that, too. More feedback is really needed. If you download it and spend time with it, drop us a line and tell us how it went.

See the Change log for changes in the latest release, or the CHANGES SVN log for a list of changes in progress for the next release..
See the THINGS TO DO file for some ideas on what needs to be done.