You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Mark Eggers <it...@yahoo.com> on 2005/09/21 02:20:08 UTC
current forrest trunk seems to be broken
This is on Windows/2000 Professional. I've not tried
it on Fedora Core 4 yet.
svn info:
Path: .
URL: http://svn.apache.org/repos/asf/forrest/trunk
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 290585
Node Kind: directory
Schedule: normal
Last Changed Author: rgardler
Last Changed Rev: 290568
Last Changed Date: 2005-09-20 14:23:19 -0700 (Tue, 20
Sep 2005)
Properties Last Updated: 2005-04-21 18:35:02 -0700
(Thu, 21 Apr 2005)
1. cd to %FORREST_HOME%\main
2. build clean
3. build
4. cd %FORREST_HOME%\plugins\<plugin-name>
5. ..\..\tools\ant\bin\ant local-deploy
6. cd %FORREST_HOME\whiteboard\plugins\<plugin-name>
7. ..\..\..\tools\ant\bin\ant local-deploy
8. cd C:\src\sites-src
9. mkdir new-site
10. cd new-site
11. forrest seed
12. forrest
Forrest fails to build the site when it hits the first
png graphic.
I've attached the log of the build as a file.
/mde/
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: current forrest trunk seems to be broken
Posted by Ross Gardler <rg...@apache.org>.
Mark Eggers wrote:
> This is on Windows/2000 Professional. I've not tried
> it on Fedora Core 4 yet.
>
> svn info:
> Path: .
> URL: http://svn.apache.org/repos/asf/forrest/trunk
> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> Revision: 290585
> Node Kind: directory
> Schedule: normal
> Last Changed Author: rgardler
> Last Changed Rev: 290568
> Last Changed Date: 2005-09-20 14:23:19 -0700 (Tue, 20
> Sep 2005)
> Properties Last Updated: 2005-04-21 18:35:02 -0700
> (Thu, 21 Apr 2005)
>
> 1. cd to %FORREST_HOME%\main
> 2. build clean
> 3. build
> 4. cd %FORREST_HOME%\plugins\<plugin-name>
> 5. ..\..\tools\ant\bin\ant local-deploy
> 6. cd %FORREST_HOME\whiteboard\plugins\<plugin-name>
> 7. ..\..\..\tools\ant\bin\ant local-deploy
> 8. cd C:\src\sites-src
> 9. mkdir new-site
> 10. cd new-site
> 11. forrest seed
> 12. forrest
>
> Forrest fails to build the site when it hits the first
> png graphic.
Can anyone reproduce this problem? I'm not currently able to try as I'm
travelling again. If so can we get it in an issue, this is a blocker.
What is the last known working revision?
Ross
Re: current forrest trunk seems to be broken
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> Hi Mark,
>
> I had a quick glance on your bash script.
>
> try:
> cd $plugin; ant local-deploy
>
> Sure you need to have ANT_HOME in your PATH.
Our instructions recommend Forrest's version of Ant:
http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#ant
-David
> BTW did you tried the ./vews.sh? Is that failing for you as well?
>
> salu2
Re: Stable trunk (was Re: current forrest trunk seems to be broken)
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 23-09-2005 a las 11:10 +0100, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
> > ...
> >
> >>X [0] linkmap.html BROKEN:
> >>org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
> >>
> >>I guess there are some plugin interactions (especially
> >>in the whiteboard area) that cause problems. That's
> >>probably why they are in the whiteboard area.
> >
> >
> > Actually I think I know what is going on. Thanks Mark for spotting this.
> > A quick workaround for you to get views running in *dynamic* mode is to
> > copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
>
> Some time ago we agreed to do all changes that could break trunk in a
> branch and only merge when they are working. We need to keep a stable trunk.
>
> We need to start doing this.
I want to remember that views are still in the whiteboard. Which means
that their are still unstable and can break. I am the last person that
want that but ...
>
> > The linkmap is broken for jx-paxth, I need to look into that. This issue
> > is the reason why "forrest site" is failing. It can take me a while
> > because I am pretty busy this days. Maybe somebody can help us out here
> > and send a patch.
>
> Is it too much to revert the changes and do this in a branch?
Yes, I am afraid yes. More so because on my local version I finished all
contracts. There is no more *.page. It will all requested by nuggets and
the dependency to the skinconf is resolved as well. I will check that in
tonight.
> That way it doesn't matter that you are busy.
Actually I hoped that somebody could give me a helping hand. Anyway this
way I am now really close to have seen all internals of forrest. ;-)
> Sure other people could provide a patch, but even if they have the time
> I'm sure they would rather be working on stuff that they need. With
> Trunk as it is nobody can work on a production site (yes that is the
> risk of working with head, but then we decided to keep trunk stable).
Actually a stable trunk is IMO not for the whiteboard. If nobody needs
views in production then there is no problem at all. ;-) BTW I do not
need "forrest site", still I will have to fix it because it is a core
functionality (and I thought views as well). BTW the linkmap is not
working probably (the reason for views being broken) and that *is* a
core functionality.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Stable trunk (was Re: current forrest trunk seems to be broken)
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
> ...
>
>>X [0] linkmap.html BROKEN:
>>org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
>>
>>I guess there are some plugin interactions (especially
>>in the whiteboard area) that cause problems. That's
>>probably why they are in the whiteboard area.
>
>
> Actually I think I know what is going on. Thanks Mark for spotting this.
> A quick workaround for you to get views running in *dynamic* mode is to
> copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
Some time ago we agreed to do all changes that could break trunk in a
branch and only merge when they are working. We need to keep a stable trunk.
We need to start doing this.
> The linkmap is broken for jx-paxth, I need to look into that. This issue
> is the reason why "forrest site" is failing. It can take me a while
> because I am pretty busy this days. Maybe somebody can help us out here
> and send a patch.
Is it too much to revert the changes and do this in a branch?
That way it doesn't matter that you are busy.
Sure other people could provide a patch, but even if they have the time
I'm sure they would rather be working on stuff that they need. With
Trunk as it is nobody can work on a production site (yes that is the
risk of working with head, but then we decided to keep trunk stable).
Ross
Re: current forrest trunk seems to be broken
Posted by Thorsten Scherler <th...@apache.org>.
El mié, 21-09-2005 a las 15:09 -0700, Mark Eggers escribió:
...
>
> X [0] linkmap.html BROKEN:
> org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
>
> I guess there are some plugin interactions (especially
> in the whiteboard area) that cause problems. That's
> probably why they are in the whiteboard area.
Actually I think I know what is going on. Thanks Mark for spotting this.
A quick workaround for you to get views running in *dynamic* mode is to
copy commons-jxpath-1.2.jar from cocoon-2.2.x into lib/core of forrest.
The linkmap is broken for jx-paxth, I need to look into that. This issue
is the reason why "forrest site" is failing. It can take me a while
because I am pretty busy this days. Maybe somebody can help us out here
and send a patch.
Cheers Mark that you gave us your feedback that is most valuable.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: current forrest trunk seems to be broken
Posted by Mark Eggers <it...@yahoo.com>.
Changing the script did not help. However, I did the
following and things work.
1. svn up (now at revision 290635)
2. cd $FORREST_HOME/main
3. ./build.sh clean
4. ./buidl.sh
5. cd $FORREST_HOME/plugins
6. build pdf output plugin only
7. verify the default environment works:
cd ~mdeggers/src/sites-src
mkdir new-site
cd new-site
forrest seed
forrest
8. Build only those plugins required for views.
cd $FORREST_HOME/etc
./views.sh
9. cd ~mdeggers/src/sites-src/views
10. forrest seed
11. make the appropriate views edits
uncomment project.skin=leather-dev
add the views plugins to the required plugin list:
project.required.plugins=
org.apache.forrest.plugin.output.pdf,
org.apache.forrest.plugin.input.viewHelper.xhtml.ls,
org.apache.forrest.plugin.output.viewHelper.xhtml,
org.apache.forrest.plugin.internal.view
12. forrest
X [0] linkmap.html BROKEN:
org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer(Lorg/apache/commons/jxpath/Pointer;)V
I guess there are some plugin interactions (especially
in the whiteboard area) that cause problems. That's
probably why they are in the whiteboard area.
I promise before posting issues like this in the
future that I'll walk through all the paths I can
think of.
I apologize for cluttering up the mailing list.
In short:
1. The current trunk generic theming works as long as
you don't include every whiteboard plugin.
2. I couldn't get views to work with the current trunk
but that seems to be a known issue?
/mde/
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: current forrest trunk seems to be broken
Posted by Mark Eggers <it...@yahoo.com>.
I'll change my script and see how that works.
Running your script under cygwin and setting up the
following environment variable:
export FORREST_HOME=C:\\src\\forrest
created the ${plugins.localDeploy-dir} again.
I think I found that problem:
<unzip
dest="${plugins.localDeploy-dir}/${plugin-name}/resources">
should be
<unzip
dest="${plugins.localDeploy.dir}/${plugin-name}/resources">
Building views with your $FORREST_HOME/etc/views.sh
now works. I'll hop back over the the Fedora side and
run the appropriate tests.
I still don't understand why building the plugins
manually on Windows/2000 Professional, or with the
script on Fedora Core 4 fails to produce a working
forrest, but letting forrest build its own plugins
works.
I'll explore that some more.
/mde/
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: current forrest trunk seems to be broken
Posted by Thorsten Scherler <th...@apache.org>.
Hi Mark,
I had a quick glance on your bash script.
try:
cd $plugin; ant local-deploy
Sure you need to have ANT_HOME in your PATH.
BTW did you tried the ./vews.sh? Is that failing for you as well?
salu2
El mié, 21-09-2005 a las 10:32 -0700, Mark Eggers escribió:
> I'll add the --noconfig and see what happens. I am
> using Sun's java instead of GNU's java as supplied by
> Fedora. My PATH is set appropriately to call Sun's
> java first. I've not had any problems until recently.
> I've also seen the same problem on Windows/2000
> Professional.
>
> Same error.
>
> I also deleted the entire forrest directory and
> checked out the same version:
>
> svn co http://svn.apache.org/repos/asf/forrest/trunk \
> -r 290585 forrest
>
> With the same error.
>
> I also noticed the directory:
>
> ${plugins.localDeploy-dir}
>
> being created for
>
> org.apache.forrest.plugin.output.htmlArea
>
> =======================
> Ah ha!!!!!! Found it.
> =======================
>
> If I build the plugins manually then forrest fails.
> This occurs with either my build script (see
> attached), or changing to the plugin directory and
> doing:
>
> $FORREST_HOME/tools/ant/bin/ant local-deploy
>
> If I let forrest build the plugins dynamically, then
> it works.
>
> Unfortunately, this doesn't currently work for the
> views environment.
>
> My Cocoon 2.1.7 environment (with the exception of JSP
> pages and one Groovy page) works fine under JDK 1.5 /
> Tomcat 5.5.9 on both Windows/2000 Professional and
> Fedora. I suspect a Jasper/Xerces issue for the JSP
> pages which can be solved by using Saxon. I don't
> know how to solve the null pointer exception, but at
> first glance it appears to be part of the same issue.
>
> /mde/
>
> --- Antonio Gallardo <ag...@agssa.net> wrote:
>
> > Hi:
> >
> > I run forrest and cocoon on FC4 since june 2005. I
> > don't have any error.
> > Please see:
> >
> > http://wiki.apache.org/cocoon/Installing
> >
> > Best Regards,
> >
> > Antonio Gallardo.
> >
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: current forrest trunk seems to be broken
Posted by Antonio Gallardo <ag...@agssa.net>.
Sorry, I forgot to tell I use the solution for FC3. I never tried the
new FC4 solution on the wiki page.
Best Regards,
Antonio Gallardo.
Mark Eggers wrote:
>I'll add the --noconfig and see what happens. I am
>using Sun's java instead of GNU's java as supplied by
>Fedora. My PATH is set appropriately to call Sun's
>java first. I've not had any problems until recently.
> I've also seen the same problem on Windows/2000
>Professional.
>
>Same error.
>
>I also deleted the entire forrest directory and
>checked out the same version:
>
>svn co http://svn.apache.org/repos/asf/forrest/trunk \
>-r 290585 forrest
>
>With the same error.
>
>I also noticed the directory:
>
>${plugins.localDeploy-dir}
>
>being created for
>
>org.apache.forrest.plugin.output.htmlArea
>
>=======================
>Ah ha!!!!!! Found it.
>=======================
>
>If I build the plugins manually then forrest fails.
>This occurs with either my build script (see
>attached), or changing to the plugin directory and
>doing:
>
>$FORREST_HOME/tools/ant/bin/ant local-deploy
>
>If I let forrest build the plugins dynamically, then
>it works.
>
>Unfortunately, this doesn't currently work for the
>views environment.
>
>My Cocoon 2.1.7 environment (with the exception of JSP
>pages and one Groovy page) works fine under JDK 1.5 /
>Tomcat 5.5.9 on both Windows/2000 Professional and
>Fedora. I suspect a Jasper/Xerces issue for the JSP
>pages which can be solved by using Saxon. I don't
>know how to solve the null pointer exception, but at
>first glance it appears to be part of the same issue.
>
>/mde/
>
>--- Antonio Gallardo <ag...@agssa.net> wrote:
>
>
>
>>Hi:
>>
>>I run forrest and cocoon on FC4 since june 2005. I
>>don't have any error.
>>Please see:
>>
>>http://wiki.apache.org/cocoon/Installing
>>
>>Best Regards,
>>
>>Antonio Gallardo.
>>
>>
>>
>
>
>
>__________________________________
>Yahoo! Mail - PC Magazine Editors' Choice 2005
>http://mail.yahoo.com
>
Re: current forrest trunk seems to be broken
Posted by Mark Eggers <it...@yahoo.com>.
I'll add the --noconfig and see what happens. I am
using Sun's java instead of GNU's java as supplied by
Fedora. My PATH is set appropriately to call Sun's
java first. I've not had any problems until recently.
I've also seen the same problem on Windows/2000
Professional.
Same error.
I also deleted the entire forrest directory and
checked out the same version:
svn co http://svn.apache.org/repos/asf/forrest/trunk \
-r 290585 forrest
With the same error.
I also noticed the directory:
${plugins.localDeploy-dir}
being created for
org.apache.forrest.plugin.output.htmlArea
=======================
Ah ha!!!!!! Found it.
=======================
If I build the plugins manually then forrest fails.
This occurs with either my build script (see
attached), or changing to the plugin directory and
doing:
$FORREST_HOME/tools/ant/bin/ant local-deploy
If I let forrest build the plugins dynamically, then
it works.
Unfortunately, this doesn't currently work for the
views environment.
My Cocoon 2.1.7 environment (with the exception of JSP
pages and one Groovy page) works fine under JDK 1.5 /
Tomcat 5.5.9 on both Windows/2000 Professional and
Fedora. I suspect a Jasper/Xerces issue for the JSP
pages which can be solved by using Saxon. I don't
know how to solve the null pointer exception, but at
first glance it appears to be part of the same issue.
/mde/
--- Antonio Gallardo <ag...@agssa.net> wrote:
> Hi:
>
> I run forrest and cocoon on FC4 since june 2005. I
> don't have any error.
> Please see:
>
> http://wiki.apache.org/cocoon/Installing
>
> Best Regards,
>
> Antonio Gallardo.
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: current forrest trunk seems to be broken
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi:
I run forrest and cocoon on FC4 since june 2005. I don't have any error.
Please see:
http://wiki.apache.org/cocoon/Installing
Best Regards,
Antonio Gallardo.
Mark Eggers wrote:
>I just tried this on Fedora Core 4. I get exactly the
>same error.
>
>I had two ideas when you mentioned a potential issue
>with the classpath. The first idea was that since Sun
>insists on putting Java in "Program Files" for
>Windows, the space was somehow creating problems.
>
>The second idea is that I have my own installation of
>ant (with ANT_HOME set and ANT_HOME/bin in my path).
>
>Here are the steps I took to reproduce this on Fedora
>Core 4.
>
>Environment
>===========
>Fedora Core 4 2.6.12-1.1447_FC4
>java 1.5.0_04-b05 in /usr/java linked from
>/usr/jdk1.5.0_04
>no CLASSPATH
>export FORREST_HOME=/home/mdeggers/src/forrest
>export PATH=$PATH:$FORREST_HOME/bin
>
>Case 1
>======
>1. svn update -r 290585
>2. cd $FORREST_HOME/main
>3. ./build.sh clean
>4. ./build.sh
>5. cd $FORREST_HOME/plugins
>6. ./build-all.sh (shell script for building all
>plugins)
>7. cd $FORREST_HOME/whiteboard/plugins
>8. ./build-all.sh (shell script for building all
>plugins)
>9. cd ~mdeggers/src/sites-src/
>10. mkdir new-site
>11. cd new-site
>12. forrest seed
>13. forrest
>
>I then unset ANT_HOME and removed ANT_HOME/bin from my
>path. I removed ~mdeggers/src/sites-src/new-site and
>did the following:
>
>Case 2
>======
>1. cd $FORREST_HOME/main
>2. ./build.sh clean
>3. ./build.sh
>4. cd $FORREST_HOME/plugins
>5. ./build-all.sh (shell script for building all
>plugins)
>6. cd $FORREST_HOME/whiteboard/plugins
>7. ./build-all.sh (shell script for building all
>plugins)
>8. cd ~mdeggers/src/sites-src/
>9. mkdir new-site
>10. cd new-site
>11. forrest seed
>12. forrest
>
>The same build error occured.
>
>I thought there might also be some issues with Java 5.
>I then tried switching to the following java version:
>
>java 1.4.2_08-b03 from /usr/j2sdk1.4.2_08
>
>I removed the 1.5 version from my PATH, added the
>1.4.2 bin directory to my PATH, and set JAVA_HOME
>appropriately.
>
>I then did the following:
>
>Case 3
>======
>1. cd $FORREST_HOME/main
>2. ./build.sh clean
>3. ./build.sh
>4. cd $FORREST_HOME/plugins
>5. ./build-all.sh (shell script for building all
>plugins)
>6. cd $FORREST_HOME/whiteboard/plugins
>7. ./build-all.sh (shell script for building all
>plugins)
>8. cd ~mdeggers/src/sites-src/
>9. mkdir new-site
>10. cd new-site
>11. forrest seed
>12. forrest
>
>Same error. This was with ANT_HOME still unset and
>$ANT_HOME/bin removed from my PATH.
>
>I have seen EOL (DOS vs. UNIX) problems cause similar
>issues in make files, but never in a Java environment.
>
>Thoughts on what I might be doing wrong (or different)
>would be greatly appreciated.
>
>/mde/
>
>--- Juan Jose Pablos <ch...@apache.org> wrote:
>
>
>
>>Mark Eggers wrote:
>>
>>
>>>This is on Windows/2000 Professional. I've not
>>>
>>>
>>tried
>>
>>
>>>it on Fedora Core 4 yet.
>>>
>>>
>>It looks a problem with classpath on your system.
>>our forrestbot builds
>>fine.
>>
>>Cheers,
>>cheche
>>
>>
>>
>>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>
Re: current forrest trunk seems to be broken
Posted by Mark Eggers <it...@yahoo.com>.
I just tried this on Fedora Core 4. I get exactly the
same error.
I had two ideas when you mentioned a potential issue
with the classpath. The first idea was that since Sun
insists on putting Java in "Program Files" for
Windows, the space was somehow creating problems.
The second idea is that I have my own installation of
ant (with ANT_HOME set and ANT_HOME/bin in my path).
Here are the steps I took to reproduce this on Fedora
Core 4.
Environment
===========
Fedora Core 4 2.6.12-1.1447_FC4
java 1.5.0_04-b05 in /usr/java linked from
/usr/jdk1.5.0_04
no CLASSPATH
export FORREST_HOME=/home/mdeggers/src/forrest
export PATH=$PATH:$FORREST_HOME/bin
Case 1
======
1. svn update -r 290585
2. cd $FORREST_HOME/main
3. ./build.sh clean
4. ./build.sh
5. cd $FORREST_HOME/plugins
6. ./build-all.sh (shell script for building all
plugins)
7. cd $FORREST_HOME/whiteboard/plugins
8. ./build-all.sh (shell script for building all
plugins)
9. cd ~mdeggers/src/sites-src/
10. mkdir new-site
11. cd new-site
12. forrest seed
13. forrest
I then unset ANT_HOME and removed ANT_HOME/bin from my
path. I removed ~mdeggers/src/sites-src/new-site and
did the following:
Case 2
======
1. cd $FORREST_HOME/main
2. ./build.sh clean
3. ./build.sh
4. cd $FORREST_HOME/plugins
5. ./build-all.sh (shell script for building all
plugins)
6. cd $FORREST_HOME/whiteboard/plugins
7. ./build-all.sh (shell script for building all
plugins)
8. cd ~mdeggers/src/sites-src/
9. mkdir new-site
10. cd new-site
11. forrest seed
12. forrest
The same build error occured.
I thought there might also be some issues with Java 5.
I then tried switching to the following java version:
java 1.4.2_08-b03 from /usr/j2sdk1.4.2_08
I removed the 1.5 version from my PATH, added the
1.4.2 bin directory to my PATH, and set JAVA_HOME
appropriately.
I then did the following:
Case 3
======
1. cd $FORREST_HOME/main
2. ./build.sh clean
3. ./build.sh
4. cd $FORREST_HOME/plugins
5. ./build-all.sh (shell script for building all
plugins)
6. cd $FORREST_HOME/whiteboard/plugins
7. ./build-all.sh (shell script for building all
plugins)
8. cd ~mdeggers/src/sites-src/
9. mkdir new-site
10. cd new-site
11. forrest seed
12. forrest
Same error. This was with ANT_HOME still unset and
$ANT_HOME/bin removed from my PATH.
I have seen EOL (DOS vs. UNIX) problems cause similar
issues in make files, but never in a Java environment.
Thoughts on what I might be doing wrong (or different)
would be greatly appreciated.
/mde/
--- Juan Jose Pablos <ch...@apache.org> wrote:
> Mark Eggers wrote:
> > This is on Windows/2000 Professional. I've not
> tried
> > it on Fedora Core 4 yet.
>
> It looks a problem with classpath on your system.
> our forrestbot builds
> fine.
>
> Cheers,
> cheche
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: current forrest trunk seems to be broken
Posted by Juan Jose Pablos <ch...@apache.org>.
Mark Eggers wrote:
> This is on Windows/2000 Professional. I've not tried
> it on Fedora Core 4 yet.
It looks a problem with classpath on your system. our forrestbot builds
fine.
Cheers,
cheche