Thats the basic premise. Slap a tag in with only a numerical ID. That maps back to a --- well lets say Trac issue number. Then you can generate a report that shows why the code was write and in response to what issue/requirement.
On 4/21/05, William Irving Zumwalt <[EMAIL PROTECTED]> wrote: > I can see lots of reasons. I like generating documentation and having it > directly map to the location where the implementation was done. Write > once, read anywhere. Very accurate documentation. Of course I'd only put > tags in the source files and stay away from writing too much text there > and write the heavier stuff elsewhere; hence, the mappings. > > >What do you mean? What is it good for? > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > xdoclet-user mailing list > xdoclet-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > -- Christopher Williams ____________________________________________ Product Manager Cryptek, Inc. [address] 1501 Moran Road Sterling, VA 20166 [phone] o: 571.434.2000 c: 703.547.7101 [web] url: www.cryptek.com aim: cryptekdcpm ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ xdoclet-user mailing list xdoclet-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-user
