Ganymede 1.0.12 released
[Posted April 28, 2004 by cook]
| From: |
| Jonathan Abbey <jonabbey-AT-arlut.utexas.edu> |
| To: |
| ganymede-announce-AT-arlut.utexas.edu |
| Subject: |
| [Ganymede Announce] Ganymede 1.0.12 released |
| Date: |
| Mon, 26 Apr 2004 22:28:04 -0500 |
Ganymede 1.0.12 is now available for download at
http://www.arlut.utexas.edu/gash2/
or
ftp://ftp.arlut.utexas.edu/pub/ganymede/
Mirrors:
ftp://planetmirror.com/pub/ganymede/ (Planet Mirror, Australia)
ftp://ftp.kddlabs.co.jp/pub/ganymede/ (KDD R&D Labs, Kamifukuoka, Saitama, Japan)
ftp://ftp2.sinica.edu.tw/pub4/ganymede/ (Academia Sinica, Taiwan)
ftp://ftp.gwdg.de/pub/misc/ganymede/ (University of Goettingen, Germany)
Ganymede is a GPL'ed metadirectory system. Ganymede provides support
for concurrent, team-based management of network directory services.
It features a multithreaded database server with support for plug-in
Java classes to customize the structure, management, and distribution
of network directory data. Ganymede allows large groups of
administrators to share administrative control over designated
portions of a master network directory database, and provides
transactional reliability and intelligent constraint management to
keep network directories consistent. Ganymede keeps complete audit
trails for all activity and can send email notification of relevant
directory changes to every member of your admin team, keeping
administrative teams coordinated and effective. Ganymede's
sophisticated graphical user interface is designed to provide a high
enough level of ease and safety of use to allow even relatively
untrained users to make changes to the directory database.
Ganymede has been designed and implemented over a seven year period to
act as the glue that holds your admin teams and your directory
services together.
--
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.
Changes in this release:
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
See ftp://ftp.arlut.utexas.edu/pub/ganymede/1.0.12/CHANGES for a
complete description of these changes.
--
-------------------------------------------------------------------------------
Jonathan Abbey jonabbey@arlut.utexas.edu
Applied Research Laboratories The University of Texas at Austin
GPG Key: 71767586 at keyserver pgp.mit.edu, http://www.ganymeta.org/workkey.gpg
(
Log in to post comments)