rubys 01/09/25 21:20:59
Modified: proposal/gump/site/xdocs status.xml
Log:
xml-fop error has been addressed!
Revision Changes Path
1.4 +0 -29 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- status.xml 2001/09/25 22:35:36 1.3
+++ status.xml 2001/09/26 04:20:59 1.4
@@ -26,40 +26,11 @@
apparently not being made in a backwards compatbile manner.</p>
</subsection>
-<!--
- <subsection name="tyrex">
- <p>Tyrex will compile cleanly with Ant 1.3 and log4j 1.0.4. It also have
- every indication that it would compile (albeit with deprecation warnings)
- and work with the latest release of log4j (1.1.3).</p>
- <p>Most of the errors are due to a Ant bug fix made during the development
- of the 1.4 release. the Tyrex source tree contains files which will not
- compile, but are to be excluded from the build. The excludes attribute
- is coded as excludes="tyrex/corba/*", but this really should be
- excludes="tyrex/corba/**" as the files to be excluded are contained in
- subdirectories</p>
- <p>The remaining errors are due to usages of interfaces which were
- deprecated in various releases of log4j and now have been removed.</p>
- <p>Three attempts have been made to contact the tyrex development team.
- On the third attempt, I received a response that these problems are
- temporary.</p>
- </subsection>
--->
-
<subsection name="scarab">
<p>For a while, scarab was trying to keep up with the evolution of
the torque component of turbine-3. Eventually, this became too disruptive
and work has continued using a snapshot of turbine. This snapshot does
not correspond to any public release or the current HEAD.</p>
- </subsection>
-
- <subsection name="xml-fop">
- <p>Batik is in the process of correcting what they have described as
- a fairly fundamental design error. This should only affect a small
- minority of batik users. Unfortunately, xml-fop is one of the users
- affects.</p>
- <p>At the present time, there is a good line of communication between
- the two projects, and the fop team understands and agrees to this change.
- They plan to step up once the changes are released.</p>
</subsection>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
