Ferdinand Soethe wrote:
Since the dispatcher test is still breaking trunk, I have now fixed some
of the problems with fo used in the dispatcher plugin.
Further tests unfortunately become impossible because
forrest crashed with the message
Exception in thread main java.lang.OutOfMemoryError:
Thorsten Scherler wrote:
On Sun, 2008-02-17 at 09:49 +0100, Ferdinand Soethe wrote:
The problem still remains that the plugins use two different properties
system which forces the dispatcher to maintain some custom code (which
it is a pity).
So we ought to make the new property system the
Thorsten Scherler wrote:
Hi all,
what is the focus/status of
org.apache.forrest.plugin.internal.xhtml2?
It was an experiment by me that was not well accepted. Status is dead.
Ross
On Mon, 2008-02-18 at 08:48 +, Ross Gardler wrote:
Ferdinand Soethe wrote:
Since the dispatcher test is still breaking trunk, I have now fixed some
of the problems with fo used in the dispatcher plugin.
Further tests unfortunately become impossible because
forrest crashed with the
On Thu, 2008-02-07 at 23:36 +, Ross Gardler wrote:
...
Why are we using skinconf for core plugins? The only plugin that should
use skinconf is a skin plugin (if it would exist)!
I'm not against breaking the dependency. I'm only against doing it in
0.3 PDF plugin, released for Forrest
On Mon, 2008-02-18 at 08:53 +, Ross Gardler wrote:
Ferdinand Soethe wrote:
I think we are ready to merge fop94 now.
Several bugs in documents and stylesheets have been fixed.
Build test for site-author and seed side passed without critical errors.
The remaining problem of some
Thorsten Scherler wrote:
On Mon, 2008-02-18 at 08:48 +, Ross Gardler wrote:
Ferdinand Soethe wrote:
Since the dispatcher test is still breaking trunk, I have now fixed some
of the problems with fo used in the dispatcher plugin.
Further tests unfortunately become impossible because
Thorsten Scherler wrote:
On Thu, 2008-02-07 at 23:36 +, Ross Gardler wrote:
...
Why are we using skinconf for core plugins? The only plugin that should
use skinconf is a skin plugin (if it would exist)!
I'm not against breaking the dependency. I'm only against doing it in
0.3 PDF plugin,
On Mon, 2008-02-18 at 08:57 +, Ross Gardler wrote:
Thorsten Scherler wrote:
On Fri, 2008-02-15 at 13:49 +0100, Thorsten Scherler wrote:
Hi all,
what is the focus/status of
org.apache.forrest.plugin.internal.xhtml2?
In the XDocs plugin we do *-to-xhtml2 in the xhtml2 plugin I
Thorsten Scherler wrote:
On Fri, 2008-02-15 at 13:49 +0100, Thorsten Scherler wrote:
Hi all,
what is the focus/status of
org.apache.forrest.plugin.internal.xhtml2?
In the XDocs plugin we do *-to-xhtml2 in the xhtml2 plugin I can find
xhtml2-to-html.
Does it makes sense to have as well
Ferdinand Soethe wrote:
I think we are ready to merge fop94 now.
Several bugs in documents and stylesheets have been fixed.
Build test for site-author and seed side passed without critical errors.
The remaining problem of some broken images will not break trunk and
probably requires some more
Thorsten Scherler wrote:
On Mon, 2008-02-18 at 08:57 +, Ross Gardler wrote:
Thorsten Scherler wrote:
On Fri, 2008-02-15 at 13:49 +0100, Thorsten Scherler wrote:
Hi all,
what is the focus/status of
org.apache.forrest.plugin.internal.xhtml2?
In the XDocs plugin we do *-to-xhtml2 in the
Great! Now we don't have to maintain two versions of this
code. Thanks.
Best regards,
Ferdinand Soethe
Thorsten Scherler wrote:
On Sun, 2008-02-17 at 09:49 +0100, Ferdinand Soethe wrote:
Since the dispatcher test is still breaking trunk, I have
now fixed some of the problems with fo used in
The pdf-plugin will not work with 0.8 as is because it was
decided to move critical libs from the plugin back into core.
Because of this, the plugin will only work with 0.8 if 0.8
gets patched.
What I haven't tested so far is if 0.8 will work with a
locally deployed plugin that is marked
would it do any harm to deliver the libs twice?
i.e. include in the 0.8 plugin (throw out for the later
versions) and in core?
I haven't had the time to test with 0.8, yet :-(
Johannes
Ferdinand Soethe schrieb:
The pdf-plugin will not work with 0.8 as is because it was decided to
move
It did not seem to do any harm when I first tested it with
head. Even the duplicate libs caused no problems as far as I
could tell.
I agree, that might be a nice solution for 0.8 users and
since we'd update the plugin to 0.9 dependant right away, it
would really only be a short term
Can we please avoid the increasing tendency to top-post. It loses the
context of the email and makes it difficult to follow things in the
archives (which is often our documentation).
Ross
Ferdinand Soethe wrote:
The pdf-plugin will not work with 0.8 as is because it was decided to
move critical libs from the plugin back into core.
I must have missed that. Why were they moved back in? What was the
problem with moving them into the plugin?
What I haven't tested so far is if
don't know what you mean (see attachment: Thunderbird gets it right)
and whom ... me?! might be Ferdinand, see below
I believe this is not intentional,
cheers
Johannes
Header bits
---
Ross' former message:
message-id= [EMAIL PROTECTED]
Ferdinand's reply:
I guess Ross was referring to me. Had to look up top post
to know that he was referring to excessive quoting.
And yes, I did. Was in a hurry and didn't clean up.
Sorry!
Add it to the sentence for merging my branch and temporarily
breaking trunk assuming lazy consensus.
Asche auf mein Haupt
On Mon, 2008-02-18 at 16:50 +0100, Ferdinand Soethe wrote:
I guess Ross was referring to me. Had to look up top post
to know that he was referring to excessive quoting.
Hmm, you both doing it. ;)
Top post means (as I understand it) to add your answer to the top and
the rest of the mails
Thorsten Scherler schrieb:
On Mon, 2008-02-18 at 16:50 +0100, Ferdinand Soethe wrote:
I guess Ross was referring to me. Had to look up top post
to know that he was referring to excessive quoting.
Hmm, you both doing it. ;)
Top post means (as I understand it) to add your answer to the top and
On Mon, 2008-02-18 at 11:44 +, Ross Gardler wrote:
Ferdinand Soethe wrote:
The pdf-plugin will not work with 0.8 as is because it was decided to
move critical libs from the plugin back into core.
I must have missed that. Why were they moved back in?
I think there was a
23 matches
Mail list logo
