Mark Eggers wrote: > I did. > > Actually, I did something much more severe. I deleted > my entire Forrest directory and pulled down a fresh > copy via subversion. > > I then did the following: > > 1) ./builddispatcher.sh in $FORREST_HOME/etc > 2) Built each of the plugins in $FORREST_HOME/plugins
No need to do that. Plugins are automatically used by default. Doing "local-deploy" of a particular plugin is only needed if you have made changes to it after its initial use. > 3) Built glossary and citations in > $FORREST_HOME/whiteboard/plugins As above. > 4) Tried to build site-author and got the following: This documentation set does not use Dispatcher by default, so the builddispatcher.sh at step 1) was not necessary. > BUILD FAILED > C:\src\forrest\main\targets\validate.xml:146: > Could not validate document > C:\src\forrest\site-author\content\xdocs\docs_0_80\glossary.xml > > I tried your method: > > 1) cd $FORREST_HOME/main > 2) ./build.sh clean > 3) ./build.sh > 4) cd ../site-author > 5) forrest clean > 6) forrest > > I had the same error as above. > > I noticed that the java.exe process never got above 32 > MB. With FOR-571, could this be a problem? I don't know, sorry. > I've tried to use forrest.jvmargs=-Xms64m -Xmx128m, > but that didn't seem to be reflected in the process > size. > > How do you pass arguments to the JVM in order to > increase the memory usage? > > As I've said in another email, if I don't validate the > xml documents everything is built properly. So i gather that you don't get the issues that Ferdinand reported. -David
