Working on the FOP-Update I started wondering, why
stylesheets and libraries for the pdf-output-plugin are
placed in core instead of the plugin directory.
If it was placed in the plugin-dir one could easily change
back between fop 0.2 and fop 0.94 by simple changing the
line in
We are almost there. The branch with FOP 94 is running
smoothly and I'm planning to merge it back by the end of
this week.
Some questions for the experts remain:
The branch changes Forrest core and the pdf-plugin
Can I do a complete merge or will the plugin have to
become a new version?
I
[
https://issues.apache.org/jira/browse/FOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563975#action_12563975
]
Ferdinand Soethe commented on FOR-413:
--
The problem seems to be within linkmap since
On Jan 30, 2008 5:53 AM, Ferdinand Soethe [EMAIL PROTECTED] wrote:
Working on the FOP-Update I started wondering, why
stylesheets and libraries for the pdf-output-plugin are
placed in core instead of the plugin directory.
If it was placed in the plugin-dir one could easily change
back
Ferdinand Soethe wrote:
We are almost there. The branch with FOP 94 is running
smoothly and I'm planning to merge it back by the end of
this week.
Cool!
So here is what I'll do:
- change version number of pdf-plugin in the branch to 0.3
- change required Forrest version number (but see
Tim Williams wrote:
On Jan 30, 2008 5:53 AM, Ferdinand Soethe [EMAIL PROTECTED] wrote:
Working on the FOP-Update I started wondering, why
stylesheets and libraries for the pdf-output-plugin are
placed in core instead of the plugin directory.
If it was placed in the plugin-dir one could easily
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 30 January 01:41 PM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2008-01-30 12:07:23
... Rendering docs in
[
https://issues.apache.org/jira/browse/FOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12564104#action_12564104
]
Ferdinand Soethe commented on FOR-413:
--
looking at linkmap.xml I see a document that
Ross Gardler wrote:
Ferdinand Soethe wrote:
We are almost there. The branch with FOP 94 is running
smoothly and I'm planning to merge it back by the end of
this week.
Cool!
Yes, congratulations.
The branch changes Forrest core and the pdf-plugin
Can I do a complete merge or will the
remove old forrestbot stuff from our zone for building old Cocoon docs
--
Key: FOR-1065
URL: https://issues.apache.org/jira/browse/FOR-1065
Project: Forrest
Issue Type:
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 31 January 04:39 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2008-01-31 04:06:46
... Rendering docs in
David Crossley wrote:
-
Affected code
-
I have found our use of jsch (see below). Please help
to find what other affected products that we use.
I have spent a lot of time on this. I now gather that
it is not just if a product uses cryptographic features.
As you can see from recent forrestbot error messages to
this dev list, the dispatcher enabled test site is failing
with out-of-memory errors.
We have not been getting all of the messages. I presume
that that is because jobs are hanging on the zone server.
I logged in and found 12 hung forrestbot
13 matches
Mail list logo
