1.2.1 release preparation

1 files changed, 35 insertions, 5 deletions

diff --git a/BUGS b/BUGS
index 29a4baf..514d59f 100644
--- a/BUGS
+++ b/BUGS
@@ -3,20 +3,36 @@ TODO List:
 
   * ivyprobe is a bit touchy about being fed somethin on standard input
     try echo "coucou" | ivyprobe ...
-  * document the new features of IvyClient, the extension to the API
+  * document the extension to the API
   * document the IVY_PING feature
+  * mêmes commandes que sous perl et C.
+  * write a domain checker
 
 -------------------------------------------------------------------------------------
 Known bugs:
 
-  * it seems not to work with jdk1.1.7A VM. ( Yannick Jestin, François Regis Colin)
-  * bus domain shortcuts ( 10:3456 instead of 10.255.255.255:3456  ) doesnt work
-    (Yannick Jestin)
+  * tests: java -DIVY_PING -DIVY_PING -classpath ../lib/ivy-java.jar:.  BenchLocal -b 228.1.2.3:4567
+    has failed once. Never reproduces
+
+
 
 -------------------------------------------------------------------------------------
 Fixed:
 
-1.0.12
+1.2.1
+  - bus.start(null)
+  - java -DIVY_PING -DIVY_PING -classpath ../lib/ivy-java.jar:. BenchLocal -t 2 -d 100
+    créé une nullpointerexception java.lang.NullPointerException
+    at fr.dgac.ivy.Ivy.stop(Ivy.java:157)
+    at BenchLocal$RML.receive(BenchLocal.java:87)
+    at fr.dgac.ivy.Ivy.callCallback(Ivy.java:348)
+    at fr.dgac.ivy.IvyClient.newParseMsg(IvyClient.java:361)
+    at fr.dgac.ivy.IvyClient.run(IvyClient.java:191)
+    at java.lang.Thread.run(Thread.java:484)
+    fixed a condition when a bus was requested to be stopped even before
+    having started its thread
+
+1.2.0
    - implement .die in Probe ( to get the same behavior as ivy-c ivyprobe ) .
      Done
    - Probe doesn't send empty strings -> it does now
@@ -48,3 +64,17 @@ Not a bug ?
   is possible that nobody has answered this broadcast by the time you start
   sending messages. Try adding an IvyApplicationListener with a callback on
   connect(IvyClient) to trigger the launching of messages
+
+  bus domain shortcuts ( 10:3456 instead of 10.255.255.255:3456  ) doesnt work
+  for UDP broadcast on my development environment. It's okay in multicast (Yannick Jestin)
+  In fact, it's a matter of network topography, not of shortcut processing.
+
+
+  Using the regression tests on the following platforms:
+      - Solaris: I've got a problem to make it run on the default local Domain
+        (127:2010). But this is not limited to the java ivy port !
+	success with jdk1.1.7A, on jdk1.2 , j2sdk1.3 and 1.4 with a multicast domain or a valid
+	UDP broadcast domain . I guess it's a routing problem once again :-\
+      - GNU/linux: ok with jdk1.3 and jdk1.4
+      - windows:  I don't know how to write tests
+