RE: FOP build

2010-12-22 Thread Eric Douglas
I don't know why my ant builds always seems to fail junit tests, but it appears 
most if not all of those tests are for the custom fonts it includes for 
whatever reason.  I print everything in one font (Lucida Typewriter) so it's 
readable and fixed width, so I'll just create my own version and hack out 
everything to do with specific fonts including the junit tests. 

-Original Message-
From: Pascal Sancho [mailto:pascal.san...@takoma.fr] 
Sent: Thursday, December 09, 2010 8:28 AM
To: fop-dev@xmlgraphics.apache.org
Subject: Re: FOP build

Hi,
Junit tests are for pre-commit purpose.
You can easily avoid them by running the right ant option:
 ant package.

see [1] for further info on running ant with fop.

[1] http://xmlgraphics.apache.org/fop/1.0/compiling.html#env-ant

Le 09/12/2010 14:08, Eric Douglas a écrit :
 Is there a way to simplify FOP?  I have the 1.0 source.  I can run the 
 ant build and it creates a new jar.  Now I tried excluding a font 
 class I don't need, and it failed the build on a junit test.  I tried 
 commenting that test out and it failed a different test.  I excluded a 
 few tests and it succeeded but it didn't create the jar.  It should 
 still be executing that step which creates the jar.  I'm passing in 
 custom fonts so I'd like to be able to save some overhead by removing 
 all of those base 14 fonts.
 

--
pascal


Re: FOP build

2010-12-09 Thread Pascal Sancho
Hi,
Junit tests are for pre-commit purpose.
You can easily avoid them by running the right ant option:
 ant package.

see [1] for further info on running ant with fop.

[1] http://xmlgraphics.apache.org/fop/1.0/compiling.html#env-ant

Le 09/12/2010 14:08, Eric Douglas a écrit :
 Is there a way to simplify FOP?  I have the 1.0 source.  I can run the
 ant build and it creates a new jar.  Now I tried excluding a font class
 I don't need, and it failed the build on a junit test.  I tried
 commenting that test out and it failed a different test.  I excluded a
 few tests and it succeeded but it didn't create the jar.  It should
 still be executing that step which creates the jar.  I'm passing in
 custom fonts so I'd like to be able to save some overhead by removing
 all of those base 14 fonts.
 

--
pascal


RE: FOP build

2010-12-09 Thread Eric Douglas
I tried commenting out the base 14 collection statement here and it created 
fop.jar but I've set it up differently than on my hone PC.
Here my ant build starts out telling me this.
 [echo] --- Apache FOP 1.0 [1999-2010] 
 [echo] See build.properties and build-local.properties for additional 
build settings
 [echo] Apache Ant version 1.7.1 compiled on June 27 2008
 [echo] VM: 14.3-b01, Sun Microsystems Inc.
 [echo] JAVA_HOME: ${env.JAVA_HOME}
 [echo] JAI Support PRESENT
 [echo] JCE Support PRESENT
 [echo] JUnit Support NOT Present - Committers are required to have JUnit 
working
 [echo] XMLUnit Support NOT Present - you can get it from 
http://xmlunit.sourceforge.net

On my home PC I believe it's saying JAI Support is not present, I'm not sure 
what that's looking for, but it says JUnit and XMLUnit support are present.  I 
can test again to let you know exactly what it complains about when JUnit is 
working but the fop.jar stops getting updated if you have the JUnit and just 
comment out this one line.

package org.apache.fop.render;
...
public abstract class PrintRenderer extends AbstractRenderer
...
public void setupFontInfo(FontInfo inFontInfo) throws FOPException {
this.fontInfo = inFontInfo;
FontManager fontManager = userAgent.getFactory().getFontManager();
FontCollection[] fontCollections = new FontCollection[] {
//new 
Base14FontCollection(fontManager.isBase14KerningEnabled()),
new CustomFontCollection(getFontResolver(), getFontList())
};
fontManager.setup(getFontInfo(), fontCollections);
}

For my purpose I shouldn't need any code referencing the base 14 fonts.  I'm 
passing in custom fonts.  I assume CustomFontCollection here will handle that.

-Original Message-
From: Pascal Sancho [mailto:pascal.san...@takoma.fr] 
Sent: Thursday, December 09, 2010 8:28 AM
To: fop-dev@xmlgraphics.apache.org
Subject: Re: FOP build

Hi,
Junit tests are for pre-commit purpose.
You can easily avoid them by running the right ant option:
 ant package.

see [1] for further info on running ant with fop.

[1] http://xmlgraphics.apache.org/fop/1.0/compiling.html#env-ant

Le 09/12/2010 14:08, Eric Douglas a écrit :
 Is there a way to simplify FOP?  I have the 1.0 source.  I can run the 
 ant build and it creates a new jar.  Now I tried excluding a font 
 class I don't need, and it failed the build on a junit test.  I tried 
 commenting that test out and it failed a different test.  I excluded a 
 few tests and it succeeded but it didn't create the jar.  It should 
 still be executing that step which creates the jar.  I'm passing in 
 custom fonts so I'd like to be able to save some overhead by removing 
 all of those base 14 fonts.
 

--
pascal