rubys 01/10/05 19:58:24
Modified: proposal/gump/site/xdocs status.xml
Log:
More recurring build failures.
Revision Changes Path
1.8 +12 -7 jakarta-alexandria/proposal/gump/site/xdocs/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/site/xdocs/status.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- status.xml 2001/10/01 00:24:36 1.7
+++ status.xml 2001/10/06 02:58:24 1.8
@@ -15,10 +15,8 @@
communicate.</p>
<subsection name="commons-latka">
- <p>Latka depends on function which was subsequently rolled back from
- httpclient. Latka development continues with a snapshot of an
- httpclient jar which does not correspond to any release of httpclient or
- the current cvs head.</p>
+ <p>Latka does not work with either the (stable) 1.0 release of
+ httpclient, nor the current (CVS head) 2.0 release.</p>
</subsection>
<subsection name="dbxml">
@@ -29,16 +27,17 @@
<subsection name="openejb">
<p>In Junit 3.7, a previously protected method was made public,
- impacting extenders of junit.textui.TestRunner.</p>
+ impacting extenders of junit.textui.TestRunner. A patch was provided
+ to them that worked with both the release that they are using (3.5)
+ and the current release. No acknowledgement of the patch was
+ received.</p>
</subsection>
-<!--
<subsection name="jakarta-velocity-test">
<p><a
href="http://cvs.apache.org/viewcvs/jakarta-velocity/src/java/org/apache/velocity/texen/ant/TexenTask.java.diff?r1=1.31&r2=1.32">This</a>
change apparently is not compatible with Velocity being multiple times
from the classpath with Ant 1.4.</p>
</subsection>
--->
<subsection name="xml-fop">
<p>Batik is in the process of correcting what they have described as
@@ -49,6 +48,12 @@
the two projects, and the fop team understands and agrees to this change.
They have already resynched once, and will try to track to the
release.</p>
+ </subsection>
+
+ <subsection name="xml-xalan2-smoketest">
+ <p>The xalan2 team has acknowledged that there will be known failures
+ until they finish up this release cycle. These failures are internal
+ to Xalan and not caused by changes to any other code base.</p>
</subsection>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]