From: Paul Hammant [mailto:[EMAIL PROTECTED] Sent: Monday, 04 March, 2002 18:02 To: [EMAIL PROTECTED] Subject: Structure of apps xdocs documents
Folks,
Currently each project has its own src/xdocs tree. They will not build at present, and before I begin work on a harmonised way of doing it we need to agree a strategy.
If we carry on in the current direction (scenario 1) , we will have each subproject building xdocs from <proj-name>/src/xdocs to <proj-name>/build/docs. We then might choose to copy those from there both to dist/docs and ../<somewhere-relative>/docs/<proj-name>. Two places because we need to consider that zip distributions and the central jakarta website are two differet places. We'd have to make sure that each subproject is capable of building xdocs completely (via stylebook, cocoon, or anakia). Thought is needed on whether we include the dependant jars for this in the subproject and similarly in the subproject's source distribution. I'll make no secret of the fact that I think the xdocs capability of "downloadable ant" sucks.
We some alternative solutions:
2) In CVS terms move all xdocs out of each sub-project and into a central "docs only" project of called, say, "docs"
Does this exist yet?
Above, you mention: /<somewhere-relative>/docs/<proj-name>
Relative to what? Is this in a different CVS module?
3) Copy xdocs out of each sub-project into the new "docs" project on a just-in-time basis for building into html.
Do you mean the docs project goes and builds docs for all of the projects? This might be best.
4) Ditch xdocs ;-)
Some things we can assume:
* We will get http://jakarta.apache.org/avalon/apps/ and below for our use.
Regards,
- Paul
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Shawn Boyce
QCOM, Inc. Quality Software is Our Business
http://www.qcominc.com
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
