ForrestBot build for forrest-seed FAILED

2011-05-18 Thread Forrestbot
Automated build for forrest-seed FAILED
Log attached.

--
Forrestbot run ended at 19 May 03:04 AM
Using Forrest 0.10-dev
Forrestbot administrator: Forrest developers
--

 [echo] 
  ... Forrest render START 2011-05-19 03:04:11
  ... Rendering docs in 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed


check-java-version:
 [echo] This is apache-forrest-0.10-dev
 [echo] Using Java 1.6 from /usr/local/jdk1.6.0/jre
 [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from 
/home/forrest/sources/forrest-trunk/tools/ant

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

echo-settings-condition:

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

unpack-skins:

init-skins:

fetch-plugins-descriptors:
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/plugins.xml
  [get] To: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml
  [get] local file date : Sun Jan 09 15:45:12 UTC 2011
  [get] Not modified - so not downloaded
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] To: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-2.xml
  [get] local file date : Wed Mar 02 00:45:49 UTC 2011
  [get] Not modified - so not downloaded
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/plugins.xml.
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
[mkdir] Created dir: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/webapp/conf
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [echo] 
  --
  Installing plugin: org.apache.forrest.plugin.output.pdf
  --
   

check-plugin:
 [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. 
Trying to update it...

init-props:

echo-settings-condition:

echo-settings:

init-proxy:

fetch-plugins-descriptors:

fetch-plugin:
 [echo] Trying to find the description of 
org.apache.forrest.plugin.output.pdf in the different descriptor files
 [echo] Using the descriptor file 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml...
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml 
to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/pluginlist2fetchbuild.xml
 [xslt] Loading stylesheet 
/home/forrest/sources/forrest-trunk/main/var/pluginlist2fetch.xsl

fetch-local-unversioned-plugin:

get-local:
 [echo] Trying to locally get org.apache.forrest.plugin.output.pdf
 [echo] Looking in local /home/forrest/sources/forrest-trunk/plugins
 [echo] Found !

init-build-compiler:

echo-init:

init:

compile:

jar:

local-deploy:
 [echo] Locally deploying org.apache.forrest.plugin.output.pdf

build:
 [echo] Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to 
configure

fetch-remote-unversioned-plugin-version-forrest:

fetch-remote-unversioned-plugin-unversion-forrest:

has-been-downloaded:

downloaded-message:

uptodate-message:

not-found-message:
 [echo] Fetch-plugin Ok, installing !

unpack-plugin:

install-plugin:

configure-plugin:

configure-output-plugin:
 [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap.new
 [xslt] Loading stylesheet 
/home/forrest/sources/forrest-trunk/main/var/pluginMountSnippet.xsl
 [move] Moving 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp

configure-plugin-locationmap:
 [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml
 to 
/home/forrest/conf

Re: managing dependencies

2011-05-18 Thread David Crossley
Brian M Dube wrote:
> David Crossley wrote:
> >
> > We are going to have the continued problem of management
> > of dependencies and supporting products.
> > 
> > There is the new project "EasyAnt" coming through the
> > Apache Incubator. 
> 
> I've joined their dev list and I'm experimenting with the product,
> with some success.
> 
> I see that Cocoon 2.1.11 and blocks are available in Maven
> repositories and thus accessible to Ivy / EasyAnt. Is stepping back to
> that version from 2.1.12-dev an acceptable approach if it means a
> dependency management tool could be used? Thoughts?

I reckon so. Going by my hazy memory, our current Forrest
does not need Cocoon-2.1.12 version. There is some potential
upgrade to FOP block there, but not yet in SVN.

We could also assist Cocoon to release 2.1.12

-David


managing dependencies

2011-05-18 Thread Brian M Dube
On Sat, Apr 30, 2011 at 04:44:52PM +1000, David Crossley wrote:
> We are going to have the continued problem of management
> of dependencies and supporting products.
> 
> There is the new project "EasyAnt" coming through the
> Apache Incubator. 

I've joined their dev list and I'm experimenting with the product,
with some success.

I see that Cocoon 2.1.11 and blocks are available in Maven
repositories and thus accessible to Ivy / EasyAnt. Is stepping back to
that version from 2.1.12-dev an acceptable approach if it means a
dependency management tool could be used? Thoughts?

-Brian


Re: Getting started with submodules

2011-05-18 Thread Brian M Dube
I have some of the build working with Apache EasyAnt (for
forrest-osgi). If there is a response on their list, I'll follow up
with some questions and pursue it further.

-Brian