Author: gadams
Date: Tue Jan 22 19:04:34 2013
New Revision: 1437102

URL: http://svn.apache.org/viewvc?rev=1437102&view=rev
Log:
FOP-2197: missing GlyphTester class in transcoder archives

Modified:
    xmlgraphics/fop/trunk/build.xml
    xmlgraphics/fop/trunk/status.xml

Modified: xmlgraphics/fop/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/build.xml?rev=1437102&r1=1437101&r2=1437102&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/build.xml (original)
+++ xmlgraphics/fop/trunk/build.xml Tue Jan 22 19:04:34 2013
@@ -564,6 +564,7 @@ list of possible build targets.
       <include name="org/apache/fop/apps/FOPException.class"/>
       <include name="org/apache/fop/apps/io/**"/>
       <include name="org/apache/fop/complexscripts/fonts/*.class"/>
+      <include name="org/apache/fop/complexscripts/util/GlyphTester.class"/>
       <include name="org/apache/fop/fo/Constants.class"/>
       <include name="org/apache/fop/fo/FOTreeBuilder.class"/>
       <include name="org/apache/fop/area/AreaTreeControl*"/>

Modified: xmlgraphics/fop/trunk/status.xml
URL: 
http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/status.xml?rev=1437102&r1=1437101&r2=1437102&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/status.xml (original)
+++ xmlgraphics/fop/trunk/status.xml Tue Jan 22 19:04:34 2013
@@ -59,6 +59,9 @@
       documents. Example: the fix of marks layering will be such a case when 
it's done.
     -->
     <release version="FOP Trunk" date="TBD">
+      <action context="Code" dev="GA" type="fix" fixes-bug="FOP-2197">
+       Missing GlyphTester class in transcoder archives.
+      </action>
       <action context="Fonts" dev="GA" type="fix" fixes-bug="FOP-2195">
        Use sparse arrays for position adjustments.
       </action>



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to