version to generate the docs. As Steven(?) already pointed
^^^ (yup)
:)
Been discussing this here with Bruno, I'm starting to change my opinion on this:
- of all the Maven/Anakia-based projects, how many actually embed the build or docs system into their CVS? Just like we might expect people to have Ant installed when they want to build Cocoon, we could expect them to install Forrest - if they don't want to build, they will get a bin/dist instead with generated (java)docs
- there's forrestbot.cocoondev.org for people who want uptodate/preview doco, though fast/immediate preview might not be what people really want
- I assume we are (I am!) tempted to do some 'bootstrap' thing, i.e. a tool requiring itself to generate its own docs, but this adds to the complexity of the doco environment, and moves attention away from the difficult part: Content & Structure
All valid points! I revoke my +10 but keep my -1 for inclusion in the current cocoon-2.x repos.
Maybe Andrew is right and it's really time for a cocoon-docs repo.
What do you think, guys? -- Torsten
