[ http://jira.public.thoughtworks.org/browse/CC-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_18833 ]
Jeffrey Fredrick commented on CC-202:
"We'll remove the 'starteam' and 'harvest' entries from the default-plugins.properties file. "
I think this was a mistake, shifting the burden of work to the users instead of the tool. (I'm answer a question on the mailing list now for someone bit by this.)
Better (imho) would to take any missing classes and generate a stub entry in the documentation pointing people to the contrib directory.
> generate configxml.html automatically
> Key: CC-202
> URL: http://jira.public.thoughtworks.org/browse/CC-202
> Project: CruiseControl
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.2.1
> Reporter: Jerome Lacoste
> Assigned To: Dan Rollo
> Priority: Trivial
> Attachments: CC-202-part2-v1.diff, configxml.html, configxml.html, configxml.html, configxml.html, Gendoc Design Proposal v2.0.pdf, net.sourceforge.cruisecontrol.ProjectConfig.xml, patch-v2.0.diff, patch-v2.1.diff, patch-v2.2.diff, patch-v2.3.diff, patch-v2.4.diff, patch-v2.5.diff, patch-v2.6.diff, patch-v2.7.diff, patch-v2.8.diff, patch-v6-part1.diff, patch-v6-part2.diff, patch_before_cleanup_and_full_conversion.diff, patch_v3.diff, patch_v4.diff, patch_v5.diff, proof-of-concept-diff.log, proof-of-concept-diff.txt, proof-of-concept-diff.txt
> Several people have expressed their desire of having such feature.
> xdoclet sounds like a good candidate for this problem. If addressed that way, this issue can be broken down in several steps:
> - identify the documentation requirements
> - create a tag specification that would allow to solve these requirements.
> We might lose some features as we will perhaps not be able to be as flexible as with the manual documentation
> - write the xdoclet tags that help to generate the intermediate XML
> - create an XSL template that generates the HTML from the intermediate XML
> - move the current configxml.html into tags inside the code
> - update the build/release process to generate the documentation
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira