On Tue, 26 Feb 2002 11:06, Rob Oxspring wrote:
> I've been pondering about integrating the report docs and wondered what
> others had to say.
Sounds great so far ;)
> I'd like to find a solution that can scale to any combination of the tools
> so the first question to ask is are there any other report / analysis tools
> out there that should be included? Checkstyle and maybe JavaNCSS spring to
> mind but what else do people use?
no idea. I could see things like reports based on jdiff results (detects
changes in external API of classes) would be useful. See
jdiff.sourceforge.org - though I only know of people on EGs that use the tool.
> In terms of output I'm envisaging a framed JavaDoc style setup with each
> package and class/file having some summary page backed up by a page per
> tool and a link to javadocs if available. For example with just junit and
> ncss being used you might get:
>
> /report
> /stylesheet.css
> /index.html
> /overview.html
> /overview.junit.html
> /overview.ncss.html
> /<package>/overview.html
> /<package>/overview.junit.html
> /<package>/overview.ncss.html
> /<package>/<class/file>.overview.html
> /<package>/<class>.overview.junit.html
> /<package>/<file>.overview.ncss.html
>
> Does this pattern fit all cases?
for class/package based reporting I think it does.
> Finally, I'm currently hoping that I can avoid writing another task and
> just build a target full of standard tasks. If this is going to work then
> some concatenation of files will surely be involved somewhere along the
> line... So can I nudge a committer to commit one of the past concat
> submissions :)
Lets see that target first :)
--
Cheers,
Pete
"You know what a dumbshit the 'average man' on the street is? Well, by
definition, half of them are even dumber than that!"
J.R. "Bob" Dobbs
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
