Chris Williams schrieb:
Was wondering if anyone has developed an xDoclet tag system that will
somehow map/display class methods back to the requirements that drove
the creation of those methods? If so please let me know,
Maybe I am wrong at the xdoclet-mailinglist for that idea:
Did you thought of
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
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 t
--- Chris Williams <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Was wondering if anyone has developed an xDoclet tag
> system that will
> somehow map/display class methods back to the
> requirements that drove
> the creation of those methods? If so please let me
> know,
What do you mean? What is it
Not that I know of, but I think that's an interesting idea.
On 4/20/05, Chris Williams <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Was wondering if anyone has developed an xDoclet tag system that will
> somehow map/display class methods back to the requirements that drove
> the creation of those me
