Mention of the bugs.

5 files changed, 76 insertions, 14 deletions

diff --git a/BUGS b/BUGS
index 4f99e86..74044fe 100644
--- a/BUGS
+++ b/BUGS
@@ -1,4 +1,18 @@
 Known bugs:
 
-  it seems not to work with jdk1.1.7A VM.
+  * it seems not to work with jdk1.1.7A VM.
 
+Fixed:
+
+  * 1.0.11: received an exception: IvyClient.sendBuffer.write failed: Relais brisé (pipe)
+  It happens while sending messages once a remote client has disconnected
+  ( fixed in 1.0.12 )
+
+Not a bug
+
+  if you send a msg just after the start, it is possible that the message
+  won't be sent. this is *not* a bug, but, hmmm, a feature. In fact, when you
+  do start(), it triggers different threads, the broadcasts are sent, and it
+  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
diff --git a/Changelog b/Changelog
index 1c5d8e7..bddb117 100644
--- a/Changelog
+++ b/Changelog
@@ -1,9 +1,18 @@
-CHANGELOG
+----------------------------------------------------------------------------------------
+1.0.12
 
+ IvyClient.sendBuffer update with silent error on a broken pipe, unless IVY_DEBUG is set
+ Ivy.libVersion goes private static final
+ IvyClient gets removed from the list of clients if there is a broken pipe.
+   Another bug fixed !
+ IvyDaemon is granted a public access on its constructor
+
+----------------------------------------------------------------------------------------
 1.0.11 mer jun  5 11:33:16 CEST 2002
 
  Just a debian package change. No java modification per se.
 
+----------------------------------------------------------------------------------------
 1.0.10 mar jun  4 19:00:32 CEST 2002
 
 TestIvy:
@@ -22,3 +31,33 @@ Probe
 jar file:
   added gnu/regexp and gnu/getopt class files withing the jar file
 
+----------------------------------------------------------------------------------------
+1.0.8
+
+  Fixed a bug in inserted in 1.0.7, added the Counter program,
+  useful if you want to have an inexact idea of the number of messages
+  circulating on the bus itself.
+
+----------------------------------------------------------------------------------------
+1.0.7
+
+  Fixed a bug in Ivy.java and IvyClient.java, causing the
+  problematic 'a(.*) (.*)' matching 'a 2' loosing the first empty matches.
+  Beware, this has a cost on effectiveness, but, hey, Ivy-java is not
+  optimized at all
+
+----------------------------------------------------------------------------------------
+1.0.6
+
+  Fixed a bug in fr.dgac.ivy.Probe, which didn't use the IVYBUS
+  property.
+
+----------------------------------------------------------------------------------------
+1.0.5
+
+  Multicast support
+
+----------------------------------------------------------------------------------------
+
+  epoch
+
diff --git a/README b/README
index c5e700f..526468b 100644
--- a/README
+++ b/README
@@ -17,14 +17,14 @@ to your usual installation directory for Java archives.
 To use ivy-java, you will need to include it in your classpath
 setting.  Typically this is done by adding an entry to your CLASSPATH
 variable setting with the full path to the JAR file, e.g.
-  csh:  % setenv CLASSPATH ${CLASSPATH}:/usr/java/lib/ivy-java-1.0.11.jar
- bash:  % export CLASSPATH=${CLASSPATH}:/usr/java/lib/ivy-java-1.0.11.jar
-  DOS:  > set CLASSPATH %CLASSPATH%;C:\Java\lib\ivy-java-1.0.11.jar
+  csh:  % setenv CLASSPATH ${CLASSPATH}:/usr/java/lib/ivy-java.jar
+ bash:  % export CLASSPATH=${CLASSPATH}:/usr/java/lib/ivy-java.jar
+  DOS:  > set CLASSPATH %CLASSPATH%;C:\Java\lib\ivy-java.jar
 Various shells and operating systems may have slightly different methods.
 Consult your Java virtual machine documentation for details.  You may also
 specify the -classpath option to the java executable, e.g.
-compile: % javac -classpath /usr/java/lib/ivy-java-1.0.11.jar MyClass.java
-execute: % java -classpath /usr/java/lib/ivy-java-1.0.11.jar MyClass
+compile: % javac -classpath /usr/java/lib/ivy-java.jar MyClass.java
+execute: % java -classpath /usr/java/lib/ivy-java.jar MyClass
 
 DOCUMENTATION
 
@@ -64,8 +64,11 @@ using and how you were using it.
 LATEST VERSION
 
 You can always obtain info about the latest version of ivy-java at
-http://www.tls.cena.fr/~jestin/ivy-java/ .  New versions are also announced on
-the ivy mailing list (see above).
+http://www.tls.cena.fr/products/ivy/download/desc/ivy-java.html
+
+New versions are also announced on the ivy mailing list (see above).
+From time to time, upstream source are put on
+http://www.tls.cena.fr/~jestin/ivy-java.html.
 
 Thanks!
 
diff --git a/debian/changelog b/debian/changelog
index bd4fe8b..ceb2663 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ivy-java (1.0.12) unstable; urgency=low
+
+  - updated the Changelog and debian changelog
+  - rewrite of the URLs to access the source on the ivy web site
+
+ -- Yannick Jestin <jestin@cena.fr>  Wed, 5 Jun 2002 18:21:26 +0200
+
 ivy-java (1.0.11) unstable; urgency=low
 
   - moved TestIvy and TestIvySwing to examples
diff --git a/debian/rules b/debian/rules
index 6c59926..7841867 100755
--- a/debian/rules
+++ b/debian/rules
@@ -30,16 +30,15 @@ debian/stamp/binary/ivy-java	: debian/stamp/build
 	cp -r src/fr $(javarep)
 	mkdirhier $(docdir)/doc/html/api 
 	( cd src; javadoc -d $(docdir)/doc/html/api *java )
-	cp -r doc/changes.html $(docdir)
+	cp -r Changelog $(docdir)
+	gzip -9 $(docdir)/Changelog
 	cp doc/ivy-java.1 $(mandir)
 	gzip -9 $(mandir)/ivy-java.1
-	rm -f $(docdir)/changes.html 
 	$(install_nonex) debian/README.Debian $(docdir)
 	$(install_nonex) BUGS README $(docdir)
 	$(install_nonex) examples/*.java $(exampledir)
 	$(install_nonex) debian/ivy-java $(docbasedir)
-	$(install_nonex) doc/changes.html $(docdir)/changelog.html
-	lynx -dump -nolist doc/changes.html > $(docdir)/changelog
-	$(gzip) $(docdir)/changelog $(docdir)/changelog.html
+	$(install_nonex) debian/changelog $(docdir)/Changelog.debian
+	$(gzip) $(docdir)/Changelog.debian
 	$(postbinary)
 	touch $@