Does it make sense for xml-fop dev'ers to standardize on a particular
directory structure for CVS? It seems that this problem might have been
averted had Glen used what I was the standard directory structure for
xml-fop development: for development purposes it is best if xml-fop builds
be built
Thanks for the help, Jeremias, on the patch problem I
had yesterday. I confirmed the problem was the
Index: sections all holding the name of a parent
directory of FOP, whose name I wasn't using for my own
local version of the software.
For the benefit of the FOP-DEV archives, should this
occur
Glen Mazza wrote:
[..]
2.) My problem with yesterday's file is that the Index
was Index:
xml-fop/src/java/org/apache/fop/render/rtf/rtflib/testdocs/SimpleLists.java,
but I don't store FOP in an parent directory named
xml-fop.
I manually edited all the indices in the patch file to
just start
