updating the forrest docs?

[Chris Hostetter <ho...@fucit.org>]

i wanted t ocommit a quick fix for LUCENE-936, but discovered i never
reinstalled forrest when i upgraded my box .... no problem, cehck the wiki
to see which version we use...

http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite

...go get forrest 0.7, install it run it ... uh oh, some problems.
looking at docs/index.html i see it was generated with forrest 0.8, no
worries ... wiki is out of date, i'll go get 0.8 now ... still some
problems...

X [0]                                     linkmap.html  BROKEN: Could not
find component for role:
[org.apache.cocoon.components.modules.input.InputModule/project]
(Key='org.apache.cocoon.components.modules.input.InputModule/project')
Total time: 0 minutes 3 seconds,  Site size: 0 Site pages: 0
Java Result: 1

...poking arround online, i see someone on the derby project seems to have
had the exact same problems i had (both with a clean install of 0.7 and
0.8)...

http://www.nabble.com/Could-not-find-component-for-role-error-t3649573.html

...the replies this guy got when emailing hte forrest users list was that
his 0.8 error had to do with not upgrading properly (aparently the
"sitemap.xmap" in documentation/ needs to be updated or removed or
something if you use 0.8)  and there was no satisfactory explanation for
the 0.7 problem.

I noticed the problem i had running 0.7 relates to the PDF plugin, and i
remembered seeing the plugin downloaded on the fly the first time i ran
0.7, so on a hunch i scp'ed the installation of forrest i have on my work
box to my home box -- SUCCESS! ... a freshly downloaded version of the PDF
plugin doesn't seem to like our xdocs, but the older version on my other
machine did.

Just one problem: this creates a lot of cruft in the commit becuase it's
back to 0.7.

Looking at the diffs for docs/index.html it seems like the site has gone
back and forth between 0.7 and 0.8 the past week or so depending on who is
updating it (gsingers is using 0.7 and buschmi is using 0.8) and not all
of the files on the trunk are actually consistent ... some were generated
with 0.7 and some with 0.8.  Which raises some questions:

1) Is it safe to say we should pick a version and stick with it, and
update all docs at the same time so we don't have a mix of versions and a
lot of commits consisting just of template changes like these...

http://svn.apache.org/viewvc/lucene/java/trunk/docs/demo.html?r1=548640&r2=548896

2) do we still want to use 0.7?  If so, does anyone understand the forrest
plugin mechanism well enough to explain how to ensure you get the "good"
version of the pdf plugin (ie: whichever one doesn't barf on our xdocs)

3) do we want to start using 0.8?  If so, then question for Michael: how
did you manage to get 0.8 to work for you with sitemap.xmap file we have
committed?  when I just flat out deleted my local copy of it, forrest 0.8
seemed to work fine -- but it's hard to be sure there were no bad side
effects since the svn diff is so big (with many files going from 0.7 to
0.8)

	?



-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

Re: updating the forrest docs?

[Chris Hostetter <ho...@fucit.org>]

: I think it makes sense to move to 0.8.

okay ... i removed the sitemap file, regened everything, and then read
through the diff to ensure there was nothing broken/missing -- the diff
seemed to be entirely related to teaks to the skinning between 0.7 and
0.8.

(but i'm still curious how michael had it working for him with the
"broken" sitemap.xmap file in place)


-Hoss

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

Re: updating the forrest docs?

[Grant Ingersoll <gs...@apache.org>]

On Jun 24, 2007, at 12:46 PM, Chris Hostetter wrote:


>
> Looking at the diffs for docs/index.html it seems like the site has  
> gone
> back and forth between 0.7 and 0.8 the past week or so depending on  
> who is
> updating it (gsingers is using 0.7 and buschmi is using 0.8) and  
> not all
> of the files on the trunk are actually consistent ... some were  
> generated
> with 0.7 and some with 0.8.  Which raises some questions:
>
> 1) Is it safe to say we should pick a version and stick with it, and
> update all docs at the same time so we don't have a mix of versions  
> and a
> lot of commits consisting just of template changes like these...
>
> http://svn.apache.org/viewvc/lucene/java/trunk/docs/demo.html? 
> r1=548640&r2=548896
>
> 2) do we still want to use 0.7?  If so, does anyone understand the  
> forrest
> plugin mechanism well enough to explain how to ensure you get the  
> "good"
> version of the pdf plugin (ie: whichever one doesn't barf on our  
> xdocs)
>
> 3) do we want to start using 0.8?  If so, then question for  
> Michael: how
> did you manage to get 0.8 to work for you with sitemap.xmap file we  
> have
> committed?  when I just flat out deleted my local copy of it,  
> forrest 0.8
> seemed to work fine -- but it's hard to be sure there were no bad side
> effects since the svn diff is so big (with many files going from  
> 0.7 to
> 0.8)

I think it makes sense to move to 0.8.

-Grant

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org