Forrestbot | 1 Feb 2008 02:42
Picon

ForrestBot build for forrest-sample-2 FAILED

Automated build for forrest-sample-2 FAILED
Log attached.

----------
Forrestbot run ended at 01 February 01:42 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2008-02-01 12:06:46
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

(Continue reading)

David Crossley | 1 Feb 2008 03:37
Picon
Favicon

Re: How to merge FOP94-branch

Ross Gardler wrote:
> Ferdinand Soethe wrote:
> >
> >If libs and stylesheets where moved to the plugin directory (where they 
> >belong) there could be two versions of the plugin
> >
> >    0.2 using old fop
> >    0.3 using fop .94
> 
> Yes, both David and I responded before the mail explaining why there 
> were manual install steps. I think  you can go with your suggestion and 
> ignore our request to change minimum Forrest version. As long as it is 
> tested in both 0.8 both 0.9 properly.
> 
> >Btw. How can we maintain two plugins of the same name but with different 
> >versions in the plugin directory?
> 
> Yes.

Ross are you talking about "using" Forrest plugins?
IIUC, Ferdinand is talking about developing the code
in svn trunk. As far as i can see there can only be
one version.

Ferdinand i don't understand why we would want to maintain
two separate versions.

-David

(Continue reading)

David Crossley (JIRA | 1 Feb 2008 04:01
Picon
Favicon

[jira] Closed: (FOR-1064) the example "Static Content" is hidden from view in seed site


     [
https://issues.apache.org/jira/browse/FOR-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley closed FOR-1064.
-------------------------------

    Resolution: Fixed

Fixed in r617337.

> the example "Static Content" is hidden from view in seed site
> -------------------------------------------------------------
>
>                 Key: FOR-1064
>                 URL: https://issues.apache.org/jira/browse/FOR-1064
>             Project: Forrest
>          Issue Type: Bug
>          Components: seed (fresh-site)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>             Fix For: 0.9-dev
>
>
> The sample document "Static Content" is hidden from display by site.xml (this change was introduced when
the samples were split into two sections).

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

David Crossley (JIRA | 1 Feb 2008 04:37
Picon
Favicon

[jira] Commented: (FOR-413) PDF: rendering fails when graphics too big - workaround inside


    [
https://issues.apache.org/jira/browse/FOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564617#action_12564617
] 

David Crossley commented on FOR-413:
------------------------------------

Both linkmap.pdf and wholesite.pdf work fine in current 0.9-dev trunk. Don't forget that there was a fix
recently in trunk for "wholesite". These issues should be discussed separately to this "graphics too
big" issue.

> PDF: rendering fails when graphics too big - workaround inside
> --------------------------------------------------------------
>
>                 Key: FOR-413
>                 URL: https://issues.apache.org/jira/browse/FOR-413
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugin: output.pdf
>    Affects Versions: 0.6
>            Reporter: Olivier Jacques
>            Assignee: Ferdinand Soethe
>         Attachments: added-wide-PNG-to-howto.patch, FOP-Test.zip, murks.fo, murks.fo, murks.zip,
recovered-files.zip, remove-double-id.patch
>
>
> When "forresting" a document that has embedded images, the PDF rendering sometimes stops with this error message:
> BROKEN: org.apache.fop.apps.FOPException: No meaningful layout in block after many attempts. 
Infinite loop is assumed.  Processing halted.
(Continue reading)

Forrestbot | 1 Feb 2008 05:00
Picon

ForrestBot build for forrest-sample-2 FAILED

Automated build for forrest-sample-2 FAILED
Log attached.

----------
Forrestbot run ended at 01 February 04:00 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2008-02-01 02:08:22
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

(Continue reading)

Forrestbot | 1 Feb 2008 05:14
Picon

ForrestBot build for forrest-sample-2 FAILED

Automated build for forrest-sample-2 FAILED
Log attached.

----------
Forrestbot run ended at 01 February 04:14 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2008-02-01 02:08:22
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

(Continue reading)

David Crossley (JIRA | 1 Feb 2008 05:23
Picon
Favicon

[jira] Created: (FOR-1066) Dispatcher started failing on seed sample site recently with out-of-memory error

Dispatcher started failing on seed sample site recently with out-of-memory error
--------------------------------------------------------------------------------

                 Key: FOR-1066
                 URL: https://issues.apache.org/jira/browse/FOR-1066
             Project: Forrest
          Issue Type: Bug
          Components: Plugin: internal.dispatcher, seed (fresh-site)
    Affects Versions: 0.9-dev
            Reporter: David Crossley
             Fix For: 0.9-dev

cd $FORREST_HOME/main                                                                                                          
./build.sh test                                                                                                                

The first stage (the skins-based site) builds fine.                                                                            
The second stage (the dispatcher-based site) hangs.

See email:
http://mail-archives.apache.org/mod_mbox/forrest-dev/200801.mbox/%3c20080131070310.GE2051 <at> igg.indexgeo.com.au%3e
Re: dispatcher hanging with out of memory errors

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

David Crossley (JIRA | 1 Feb 2008 05:25
Picon
Favicon

[jira] Updated: (FOR-1066) Dispatcher started failing on seed sample site recently with out-of-memory error


     [
https://issues.apache.org/jira/browse/FOR-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-1066:
--------------------------------

    Component/s: zones.a.o administration

When this is fixed, remember to turn the forrestbot cron job "forrest-sample-2" on again.

> Dispatcher started failing on seed sample site recently with out-of-memory error
> --------------------------------------------------------------------------------
>
>                 Key: FOR-1066
>                 URL: https://issues.apache.org/jira/browse/FOR-1066
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugin: internal.dispatcher, seed (fresh-site), zones.a.o administration
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>             Fix For: 0.9-dev
>
>
> cd $FORREST_HOME/main                                                                                                          
> ./build.sh test                                                                                                                
>                                                                                                                                
> The first stage (the skins-based site) builds fine.                                                                            
> The second stage (the dispatcher-based site) hangs.
> See email:
(Continue reading)

Gav.... | 1 Feb 2008 08:53
Picon

Convert html site docs to xdoc etc

Hi All,

Im helping a bit with getting stdcxx site converted to using Forrest.
The simple docs on the main part of the site are done.

Martin has asked if it is possible to convert other docs [1][2] so that
they can be integrated into the Forrest source xdoc format.

There is an awful lot of pages in those docs so an automated way to do this
would be great. Once converted to xdoc I guess after that it is a manual
process to put the pages into tabs.xml and site.xml etc.

The current 'new' site has been started and Martin has put it up in his own
area [3] as a sandbox until forrest deploy etc has been worked out.

Any ideas ?

Thanks

Gav...

[1] - http://stdcxx.apache.org/doc/stdlibref/index.html

[2] - http://stdcxx.apache.org/doc/stdlibug/index.html

[3] - http://people.apache.org/~sebor/stdcxx/forrest-site/

Ferdinand Soethe | 1 Feb 2008 10:54
Picon
Favicon

Re: [jira] Commented: (FOR-413) PDF: rendering fails when graphics too big - workaround inside

David Crossley (JIRA) wrote:

> Both linkmap.pdf and wholesite.pdf work fine in current
> 0.9-dev trunk. 

Nevertheless Forrest generates invalid xml here and this 
should be adressed, shouldn't it?

> Don't forget that there was a fix recently
> in trunk for "wholesite". These issues should be
> discussed separately to this "graphics too big" issue.

I'll try to find that on the list and see if that was after 
I created the branch. If so I'll fix that in the branch to.

Best regards,
Ferdinand Soethe


Gmane