To use this utility it will require modification of our own Perl modules found 
on the FOP SVN site. Whether that requires just a change to the patterns 
( file) or the more complicated requirement of writing our own pattern 
subroutine (in the I am not yet sure. Unfortunately though I'll have 
to park this as I currently have no more time I can spend on it but as I said 
will keep my eye on it and let you know if anything progresses.

In the meantime I am guessing there will be a vote to release fairly soon which 
will result in the documentation needing to be updated.

> Subject: Re: FOP Release Automation
> From:
> Date: Tue, 15 Jul 2014 07:53:19 -0700
> To:
> On Jul 15, 2014, at 7:46 AM, Glenn Adams <> wrote:
> > I suppose it depends on whether or not we need to hack perl to use the 
> > facility. If there is any alternative that doesn't use perl, then that 
> > would be preferable.
> > 
> > Frankly, I've never been happy with the new MD based documentation, though 
> > Clay has spent an inordinate amount of time tweaking it.
> Yeah... It's not my favorite either, but at least edits are pretty quick, 
> saved to SVN and we've got a solution to incorporate javadoc, etc. 
> In the meantime, please let me know when we're ready to update the 
> documentation for the Release. It doesn't take me very long to go through the 
> code to make these types of batch edits. I'm good at this, and who knows, I 
> might even spend the time to write some bash script to help us with the 
> deployment! (you don't have anything against BASH, do ya Glenn?) :-p) (I 
> think that's how to write a smiley with a tongue-in-cheek? :-D)

Reply via email to