[GUMP@brutus]: Project xml-fop (in module xml-fop) failed

2005-01-10 Thread Sam Ruby
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop :  XSL-FO (Formatting Objects) processor


Full details are available at:
http://brutus.apache.org/gump/public/xml-fop/xml-fop/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [fop.jar] identifier set to project name
 -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/xml-fop/build/test-classes]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://brutus.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html
Work Name: build_xml-fop_xml-fop (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 20 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main 
-Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only gump 
[Working Directory: /usr/local/gump/public/workspace/xml-fop]
CLASSPATH: 

Re: cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr TraitSetter.java BlockLayoutManager.java

2005-01-10 Thread Simon Pepping
Section 5.3.2 of the spec is really hard to understand. I combine it
with 5.1.4 about Inheritance. Then my guess is this:

fo:block margin-left=1pcA test file
  fo:inline-container start-indent=1.5pc
fo:block margin-left=1pcA test file/fo:block
  /fo:inline-container
/fo:block

The computed value of start-indent on the outer block is 'start-indent
= inherited_value_of(start-indent) + margin-corresponding +
padding-corresponding + border-corresponding-width' = 0 + 1pc + 0 +
0. The computed value of start-indent on the inner block is
'start-indent = inherited_value_of(start-indent) +
margin-corresponding + padding-corresponding +
border-corresponding-width' = 1.5pc + 1pc + 0 + 0.

In this case:

fo:block margin-left=1pcA test file
  fo:inline-container
fo:block margin-left=1pcA test file/fo:block
  /fo:inline-container
/fo:block

the computed value of start-indent on the outer block is 'start-indent
= inherited_value_of(start-indent) + margin-corresponding +
padding-corresponding + border-corresponding-width' = 0 + 1pc + 0 +
0. The computed value of start-indent on the inner block is
'start-indent = inherited_value_of(start-indent) +
margin-corresponding + padding-corresponding +
border-corresponding-width' = 1pc + 1pc + 0 + 0. The inherited value
uses the calculated value (sect. 5.1.4). That is the value that should
be returned by
pList.getParentPropertyList().get(Constants.PR_START_INDENT).getLength().

The inherited value should not be stored, but used in the computation
of the property value. This should be implemented by the property
maker.

When I run the above examples in a debugger, I find that the computed
start-indent values CommonMarginBlock.startIndent are exactly like I
argue above they should be. There does not seem to be a need to add
the inherited value later; the property maker already has done so. See
IndentPropertyMaker.compute(PropertyList). It uses
propertyList.getInherited(baseMaker.propId).getNumeric()) to get the
inherited value. Earlier FOP developers understood this part well.

If you find wrong results, then the problem must be elsewhere.

Is there a book or treatise on these subjects, where we can read how a
knowledgeable author interprets these difficult parts of the spec?

Regards, Simon

On Fri, Jan 07, 2005 at 09:26:15AM +0100, Jeremias Maerki wrote:
 Finn or Simon,
 
 would you please check if it is acceptable to put the inherited values
 directly into the CommonMarginBlock? It might have been cleaner to
 always get the value via the parent FO but I think in this case it helps
 simplifying the code in TraitSetter and BlockLayoutManager.
 
 On 07.01.2005 09:21:21 jeremias wrote:
  jeremias2005/01/07 00:21:21
  
Modified:src/java/org/apache/fop/fo/properties CommonMarginBlock.java
 src/java/org/apache/fop/layoutmgr TraitSetter.java
  BlockLayoutManager.java
Log:
Bugfix for start-indent calculation for nested blocks. The inherited 
  start-indent wasn't taken into account as described in 5.3.2 of the spec.
Minor style and javadoc improvements on the way.
 
 snip/
 
Revision  ChangesPath
1.5   +34 -2 
  xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBlock.java

Index: CommonMarginBlock.java
===
RCS file: 
  /home/cvs/xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBlock.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- CommonMarginBlock.java28 Oct 2004 10:00:24 -  1.4
+++ CommonMarginBlock.java7 Jan 2005 08:21:21 -   1.5
@@ -1,5 +1,5 @@
 /*
- * Copyright 1999-2004 The Apache Software Foundation.
+ * Copyright 1999-2005 The Apache Software Foundation.
  * 
  * Licensed under the Apache License, Version 2.0 (the License);
  * you may not use this file except in compliance with the License.
@@ -70,6 +70,16 @@
 public Length endIndent;
 
 /**
+ * The inherited start-indent property.
+ */
+public Length inheritedStartIndent;
+
+/**
+ * The inherited end-indent property.
+ */
+public Length inheritedEndIndent;
+
+/**
  * Create a CommonMarginBlock object.
  * @param pList The PropertyList with propery values.
  */
@@ -84,5 +94,27 @@
 
 startIndent = pList.get(Constants.PR_START_INDENT).getLength();
 endIndent = pList.get(Constants.PR_END_INDENT).getLength();
+
+if (!pList.getFObj().generatesReferenceAreas()) {
+inheritedStartIndent = pList.getParentPropertyList()
+.get(Constants.PR_START_INDENT).getLength();
+inheritedEndIndent = pList.getParentPropertyList()
+.get(Constants.PR_END_INDENT).getLength();
+}
+}
 
 snip/
 

Re: cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr TraitSetter.java BlockLayoutManager.java

2005-01-10 Thread Glen Mazza
BTW, would Jeremias' proposal effect future
implementation of the property value functions[1]?

Thanks,
Glen

[1]
http://www.w3.org/TR/2001/REC-xsl-20011015/slice5.html#section-N8624-Property-Value-Functions

--- Simon Pepping [EMAIL PROTECTED] wrote:

 Section 5.3.2 of the spec is really hard to
 understand. I combine it
 with 5.1.4 about Inheritance. Then my guess is this:
 
 fo:block margin-left=1pcA test file
   fo:inline-container start-indent=1.5pc
 fo:block margin-left=1pcA test
 file/fo:block
   /fo:inline-container
 /fo:block
 
 The computed value of start-indent on the outer
 block is 'start-indent
 = inherited_value_of(start-indent) +
 margin-corresponding +
 padding-corresponding + border-corresponding-width'
 = 0 + 1pc + 0 +
 0. The computed value of start-indent on the inner
 block is
 'start-indent = inherited_value_of(start-indent) +
 margin-corresponding + padding-corresponding +
 border-corresponding-width' = 1.5pc + 1pc + 0 + 0.
 
 In this case:
 
 fo:block margin-left=1pcA test file
   fo:inline-container
 fo:block margin-left=1pcA test
 file/fo:block
   /fo:inline-container
 /fo:block
 
 the computed value of start-indent on the outer
 block is 'start-indent
 = inherited_value_of(start-indent) +
 margin-corresponding +
 padding-corresponding + border-corresponding-width'
 = 0 + 1pc + 0 +
 0. The computed value of start-indent on the inner
 block is
 'start-indent = inherited_value_of(start-indent) +
 margin-corresponding + padding-corresponding +
 border-corresponding-width' = 1pc + 1pc + 0 + 0. The
 inherited value
 uses the calculated value (sect. 5.1.4). That is the
 value that should
 be returned by

pList.getParentPropertyList().get(Constants.PR_START_INDENT).getLength().
 
 The inherited value should not be stored, but used
 in the computation
 of the property value. This should be implemented by
 the property
 maker.
 
 When I run the above examples in a debugger, I find
 that the computed
 start-indent values CommonMarginBlock.startIndent
 are exactly like I
 argue above they should be. There does not seem to
 be a need to add
 the inherited value later; the property maker
 already has done so. See
 IndentPropertyMaker.compute(PropertyList). It uses

propertyList.getInherited(baseMaker.propId).getNumeric())
 to get the
 inherited value. Earlier FOP developers understood
 this part well.
 
 If you find wrong results, then the problem must be
 elsewhere.
 
 Is there a book or treatise on these subjects, where
 we can read how a
 knowledgeable author interprets these difficult
 parts of the spec?
 
 Regards, Simon
 
 On Fri, Jan 07, 2005 at 09:26:15AM +0100, Jeremias
 Maerki wrote:
  Finn or Simon,
  
  would you please check if it is acceptable to put
 the inherited values
  directly into the CommonMarginBlock? It might have
 been cleaner to
  always get the value via the parent FO but I think
 in this case it helps
  simplifying the code in TraitSetter and
 BlockLayoutManager.
  
  On 07.01.2005 09:21:21 jeremias wrote:
   jeremias2005/01/07 00:21:21
   
 Modified:   
 src/java/org/apache/fop/fo/properties
 CommonMarginBlock.java
  src/java/org/apache/fop/layoutmgr
 TraitSetter.java
   BlockLayoutManager.java
 Log:
 Bugfix for start-indent calculation for nested
 blocks. The inherited start-indent wasn't taken into
 account as described in 5.3.2 of the spec.
 Minor style and javadoc improvements on the
 way.
  
  snip/
  
 Revision  ChangesPath
 1.5   +34 -2

xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBlock.java
 
 Index: CommonMarginBlock.java


===
 RCS file:

/home/cvs/xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBlock.java,v
 retrieving revision 1.4
 retrieving revision 1.5
 diff -u -r1.4 -r1.5
 --- CommonMarginBlock.java  28 Oct 2004
 10:00:24 -1.4
 +++ CommonMarginBlock.java  7 Jan 2005 08:21:21
 - 1.5
 @@ -1,5 +1,5 @@
  /*
 - * Copyright 1999-2004 The Apache Software
 Foundation.
 + * Copyright 1999-2005 The Apache Software
 Foundation.
   * 
   * Licensed under the Apache License, Version
 2.0 (the License);
   * you may not use this file except in
 compliance with the License.
 @@ -70,6 +70,16 @@
  public Length endIndent;
  
  /**
 + * The inherited start-indent property.
 + */
 +public Length inheritedStartIndent;
 +
 +/**
 + * The inherited end-indent property.
 + */
 +public Length inheritedEndIndent;
 +
 +/**
   * Create a CommonMarginBlock object.
   * @param pList The PropertyList with
 propery values.
   */
 @@ -84,5 +94,27 @@
  
  startIndent =
 pList.get(Constants.PR_START_INDENT).getLength();
  endIndent =
 

Re: cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr TraitSetter.java BlockLayoutManager.java

2005-01-10 Thread Glen Mazza
--- Glen Mazza [EMAIL PROTECTED] wrote:

 BTW, would Jeremias' proposal 
 effect future
  ^^

oopsaffect ;)

Glen



RE: cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr TraitSetter.java BlockLayoutManager.java

2005-01-10 Thread Goel, Nitesh
In the region body I am making a table. I want the table header(that
row) to be repeated on subsequent pages. How to do that?

-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 11, 2005 2:55 AM
To: fop-dev@xml.apache.org
Subject: Re: cvs commit: xml-fop/src/java/org/apache/fop/layoutmgr
TraitSetter.java BlockLayoutManager.java

BTW, would Jeremias' proposal effect future
implementation of the property value functions[1]?

Thanks,
Glen

[1]
http://www.w3.org/TR/2001/REC-xsl-20011015/slice5.html#section-N8624-Pro
perty-Value-Functions

--- Simon Pepping [EMAIL PROTECTED] wrote:

 Section 5.3.2 of the spec is really hard to
 understand. I combine it
 with 5.1.4 about Inheritance. Then my guess is this:
 
 fo:block margin-left=1pcA test file
   fo:inline-container start-indent=1.5pc
 fo:block margin-left=1pcA test
 file/fo:block
   /fo:inline-container
 /fo:block
 
 The computed value of start-indent on the outer
 block is 'start-indent
 = inherited_value_of(start-indent) +
 margin-corresponding +
 padding-corresponding + border-corresponding-width'
 = 0 + 1pc + 0 +
 0. The computed value of start-indent on the inner
 block is
 'start-indent = inherited_value_of(start-indent) +
 margin-corresponding + padding-corresponding +
 border-corresponding-width' = 1.5pc + 1pc + 0 + 0.
 
 In this case:
 
 fo:block margin-left=1pcA test file
   fo:inline-container
 fo:block margin-left=1pcA test
 file/fo:block
   /fo:inline-container
 /fo:block
 
 the computed value of start-indent on the outer
 block is 'start-indent
 = inherited_value_of(start-indent) +
 margin-corresponding +
 padding-corresponding + border-corresponding-width'
 = 0 + 1pc + 0 +
 0. The computed value of start-indent on the inner
 block is
 'start-indent = inherited_value_of(start-indent) +
 margin-corresponding + padding-corresponding +
 border-corresponding-width' = 1pc + 1pc + 0 + 0. The
 inherited value
 uses the calculated value (sect. 5.1.4). That is the
 value that should
 be returned by

pList.getParentPropertyList().get(Constants.PR_START_INDENT).getLength()
.
 
 The inherited value should not be stored, but used
 in the computation
 of the property value. This should be implemented by
 the property
 maker.
 
 When I run the above examples in a debugger, I find
 that the computed
 start-indent values CommonMarginBlock.startIndent
 are exactly like I
 argue above they should be. There does not seem to
 be a need to add
 the inherited value later; the property maker
 already has done so. See
 IndentPropertyMaker.compute(PropertyList). It uses

propertyList.getInherited(baseMaker.propId).getNumeric())
 to get the
 inherited value. Earlier FOP developers understood
 this part well.
 
 If you find wrong results, then the problem must be
 elsewhere.
 
 Is there a book or treatise on these subjects, where
 we can read how a
 knowledgeable author interprets these difficult
 parts of the spec?
 
 Regards, Simon
 
 On Fri, Jan 07, 2005 at 09:26:15AM +0100, Jeremias
 Maerki wrote:
  Finn or Simon,
  
  would you please check if it is acceptable to put
 the inherited values
  directly into the CommonMarginBlock? It might have
 been cleaner to
  always get the value via the parent FO but I think
 in this case it helps
  simplifying the code in TraitSetter and
 BlockLayoutManager.
  
  On 07.01.2005 09:21:21 jeremias wrote:
   jeremias2005/01/07 00:21:21
   
 Modified:   
 src/java/org/apache/fop/fo/properties
 CommonMarginBlock.java
  src/java/org/apache/fop/layoutmgr
 TraitSetter.java
   BlockLayoutManager.java
 Log:
 Bugfix for start-indent calculation for nested
 blocks. The inherited start-indent wasn't taken into
 account as described in 5.3.2 of the spec.
 Minor style and javadoc improvements on the
 way.
  
  snip/
  
 Revision  ChangesPath
 1.5   +34 -2

xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBlock.java
 
 Index: CommonMarginBlock.java


===
 RCS file:

/home/cvs/xml-fop/src/java/org/apache/fop/fo/properties/CommonMarginBloc
k.java,v
 retrieving revision 1.4
 retrieving revision 1.5
 diff -u -r1.4 -r1.5
 --- CommonMarginBlock.java  28 Oct 2004
 10:00:24 -1.4
 +++ CommonMarginBlock.java  7 Jan 2005 08:21:21
 - 1.5
 @@ -1,5 +1,5 @@
  /*
 - * Copyright 1999-2004 The Apache Software
 Foundation.
 + * Copyright 1999-2005 The Apache Software
 Foundation.
   * 
   * Licensed under the Apache License, Version
 2.0 (the License);
   * you may not use this file except in
 compliance with the License.
 @@ -70,6 +70,16 @@
  public Length endIndent;
  
  /**
 + * The inherited start-indent property.
 + */
 +public Length inheritedStartIndent;
 +
 +/**
 + * The inherited end-indent property.