[JIRA] Commented: (CC-202) generate configxml.html automatically

    [ http://jira.public.thoughtworks.org/browse/CC-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_19055 ] 

Dan Rollo commented on CC-202:
------------------------------

Hi Seth,

I also get skipped hunks when applying patch b. I applied patch b using IntelliJ IDEA's built in tools, and it appears to be happy...go figure. Could be some windows/*nix voodoo going on.

Anyways, it looks great and I'm ready to commit it, however, I'm getting a test failure NoPluginParsingErrorsTest.testParsingErrors() regarding: Error - Could not read from examples file: src/net/sourceforge/cruisecontrol/bootstrappers/AntBootstrapper.examples.html
src/net/sourceforge/cruisecontrol/publishers/AntPublisher.html
src/net/sourceforge/cruisecontrol/publishers/AntPublisher.examples.html

Nice test! It caught the missing files.

I'm guessing these files exists on your local machine, but you forgot to include it in the patch? Going on that assumption, I've added an empty version of the files, and will commit the current patch once the tests pass. Please do attach the "real" versions of the missing html files (or tell me if my assumptions are wrong).

Dan

> 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-v2.9-output.txt, patch-v2.9.diff, patch-v2.9b.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

        

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb