Hi,
On 15/07/14 16:53, Clay Leeds wrote:
On Jul 15, 2014, at 7:46 AM, Glenn Adams gl...@skynav.com 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
Subject: New FOP Release [was: Re: FOP Release Automation]
Hi,
On 15/07/14 16:53, Clay Leeds wrote:
On Jul 15, 2014, at 7:46 AM, Glenn Adams gl...@skynav.com 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
I prefer python but bash is fine. OTOH, anything written by Larry Wall
should be avoided like the plague.
On Tue, Jul 15, 2014 at 8:53 AM, Clay Leeds the.webmaes...@gmail.com
wrote:
On Jul 15, 2014, at 7:46 AM, Glenn Adams gl...@skynav.com wrote:
I suppose it depends on whether or not we
.
Subject: Re: FOP Release Automation
From: the.webmaes...@gmail.com
Date: Tue, 15 Jul 2014 07:53:19 -0700
To: fop-dev@xmlgraphics.apache.org
On Jul 15, 2014, at 7:46 AM, Glenn Adams gl...@skynav.com wrote:
I suppose it depends on whether or not we need to hack perl to use the
facility
then that copy would become out of date.
We could always shutdown the web interface, but I don't think too many
people would be happy with that ;-)
Regards,
Robert
From: simonsteiner1...@gmail.com
To: fop-dev@xmlgraphics.apache.org
Subject: RE: FOP Release Automation
...@gmail.com mailto:simonsteiner1...@gmail.com
To: fop-dev@xmlgraphics.apache.org
mailto:fop-dev@xmlgraphics.apache.org
Subject: RE: FOP Release Automation
Date: Fri, 30 May 2014 14:48:15 +0100
Hi,
Simple way is to store docs inside fop repo:
Fop/docs/index.markdown
Inside markdown file you reference
Hi,
After investigating your suggestions Clay I have found that svn-hooks can't be
used for the purpose we require unfortunately as it may lead to problems with
how SVN operates and also may have some unexpected results with files being
committed. This is stated in the documentation under
out of date.
We could always shutdown the web interface, but I don't think too many people
would be happy with that ;-)
Regards,
Robert
From: simonsteiner1...@gmail.com
To: fop-dev@xmlgraphics.apache.org
Subject: RE: FOP Release Automation
Date: Fri, 30 May 2014 14:48:15 +0100
@xmlgraphics.apache.org
Subject: Re: FOP Release Automation
Agreed, ‘some’ people wouldn’t be happy with that. ;-)
I wonder if the CMS Web interface could be extended to allow for a few keywords
like FOP_VERSION, FOP_REVISION, FOP_BRANCH, etc.
The CMS tool's WYSIWYG interface indicates it uses the Wysiwym MarkDown
a find / replace on say trunk
and replacing with 2.0 would be an option (with some caveats), but I'll
investigate the other methods first.
I'll keep you posted.
Regards,
Robert Meyer
Subject: Re: FOP Release Automation
From: the.webmaes...@gmail.com
Date: Tue, 27 May 2014 21:33:32 -0700
Hi,
The FOP package should not embed the whole website, but only the
documentation part, more precisely only the relevant version folder.
Currently, FOP doc folder is referenced as svn:externals in FOP repo,
resulting on extra irrelevant info, such as other versions,
miscellaneous processes,
Thank you for looking at this, Robert. I'll take a look at MarkDown solutions
as well.
Cheers!
Clay
--
My religion is simple. My religion is kindness.
- HH The Dalai Lama of Tibet
On May 21, 2014, at 2:24 AM, Robert Meyer rme...@hotmail.co.uk wrote:
Hi All,
I've been asked to look at
12 matches
Mail list logo
