#23 Simplify reporting ant task

Current Release
closed
Matt Albrecht
5
2004-03-20
2004-02-21
Matt Albrecht
No

Based on the changes to the post-compiler task, the
coverage report task needs to be a bit easier to use.

Also, some of the verbosity levels need to be reduced
to "debug".

I'm envisioning (currently) something along the lines of:
<grobo-report logdir="${dir.coverage}"
outdir="${dir.coverage}/reports">
<source name="source-linked">
<title>Blah blah blah</title>
<footer>Blah blah blah</title>
<home link="http://mysite.com"
text="mysite.com" />
<css file="mine.css" />
</source>

<simple removeempty="true" />

<xsl outfile="x" style="mine.xsl">
<param key="x" value="y" />
</xsl>
</grobo-report>

Discussion

  • Matt Albrecht
    Matt Albrecht
    2004-02-21

    Logged In: YES
    user_id=171822

    Also, allow for an option to archive the report XML file in
    a historical directory, so that a future style could do a
    historical comparison.

     
  • Matt Albrecht
    Matt Albrecht
    2004-03-14

    Logged In: YES
    user_id=171822

    See feature requests 914410 and 901586. I'd like to make
    these kind of like the JUnit task - it can optionally fail,
    and also set properties on a failure. It seems to me like
    the optimal way to detect failures is while the report is
    being created, but maybe not.

    I'll be able to sope this better as I'm developing this task
    (which I'm starting now).

     
  • Matt Albrecht
    Matt Albrecht
    2004-03-20

    • status: open --> closed
     
  • Matt Albrecht
    Matt Albrecht
    2004-03-20

    Logged In: YES
    user_id=171822

    Added to GroboCoverage 1.1.0.

    This is now finished.