ajack 2004/02/13 15:16:12 Modified: blog/SuccessStories xml-batik.txt Log: We'll get better at these, keep a consistent thread (copying gump mailig list),
etc. Revision Changes Path 1.4 +28 -5 jakarta-gump/blog/SuccessStories/xml-batik.txt Index: xml-batik.txt =================================================================== RCS file: /home/cvs/jakarta-gump/blog/SuccessStories/xml-batik.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- xml-batik.txt 13 Feb 2004 19:18:36 -0000 1.3 +++ xml-batik.txt 13 Feb 2004 23:16:12 -0000 1.4 @@ -1,12 +1,35 @@ PREVIEW Rhino team provides fixes for batik <p> -Thanks to the <a href="http://www.mozilla.org/rhino/">Rhino</a> team for -fixing the abstract class which was causing the build of -<a href="http://xml.apache.org/batik/index.html">batik</a> to fail in gump. +With the recent restart of Gump nagging, the community has been making a push to +improve <A href="http://lsd.student.utwente.nl/gump/#Project+Summary">health of + +interactions</a>. +</p> +<p> +<a href="http://xml.apache.org/batik/index.html">XML Batik</a> was observered to + +go down, and they were notified. Their analysis led them to beleive that <a + +href="http://www.mozilla.org/rhino/">Rhino</a> had +<a + +href="http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]& + +msgId=1341462">broken backwards compatibility</a>. The <a + +href="http://www.mozilla.org/rhino/">Rhino</a> team agreed, and commit a change to + +<a + +href="http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]& + +msgNo=3934">restored backwards compatibility</a>. </p> <p> -Today batik has +<a href="http://xml.apache.org/batik/index.html">XML Batik</a> began to <a href="http://lsd.student.utwente.nl/gump/xml-batik/index.html" ->built properly</a>. +>build properly</a> again, and <b>a jar discontinuity was resolved</b> before it + +cause grief.</b> </p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
