ivy-java (1.0.10-1) unstable; urgency=low

  - TestIvy and Probe System.exit on bus die
  - IvyWatcher and IvyClient
     * isInDomain() is wrong  in multicast. I've removed it
     * there was a remanence effect in the datagrampacket buffer. I clean it up after each message
     * cleaned up the getDomain() and getPort() code 
     * I allow multiple domains
     * I Removed the CPU eating loop on soTimeOut, with a vector of broadcast listeners

 -- Yannick Jestin <jestin@cena.fr>  Thu, 4 Jun 2002 19:06:15 +0200

ivy-java (1.0.9-1) unstable; urgency=low

  * there were still some bugs in the protocol handling
  * the die semantics is now abided by our java clients
  * code cleaning
  * the real examples have been put in examples

 -- Yannick Jestin <jestin@cena.fr>  Thu, 7 Mar 2002 15:16:08 +0200

ivy-java (1.0.8-1) unstable; urgency=low

  * don't use StringTokenizer any more, it is too buggy and version dependent
  * new ivyTranslater example
  * new Counter program (in examples ) to show how to count
    ivy messages
  * cleaned IVY_DEBUG handling in Ivy.java
  * added a global variable for protocol version and library version
  * improved gnu.getopt.GetOpt support

 -- Yannick Jestin <jestin@cena.fr>  Wen, 6 Mar 2002 14:04:08 +0200

ivy-java (1.0.7-1) unstable; urgency=low

  * Corrects the Bug of StringTokenizer ( no Bug tracking system yet )
    reported on the mailing list.

 -- Yannick Jestin <jestin@cena.fr>  Wen, 10 Oct 2001 13:35:08 +0200

ivy-java (1.0.5-2) unstable; urgency=low

  * Fix problems in the package building

 -- Yannick Jestin <jestin@cena.fr>  Wen, 8 Aug 2001 16:43:08 +0200

ivy-java (1.0.5-1) unstable; urgency=low

  * Initial Release.

 -- Yannick Jestin <jestin@cena.fr>  Mon, 6 Aug 2001 17:17:08 +0200