You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "John Didion (JIRA)" <ji...@codehaus.org> on 2006/11/02 00:19:51 UTC

[jira] Updated: (CONTINUUM-566) Build numbers are essential

     [ http://jira.codehaus.org/browse/CONTINUUM-566?page=all ]

John Didion updated CONTINUUM-566:
----------------------------------

    Attachment: add-build-number-to-mail-subject.diff

> Build numbers are essential
> ---------------------------
>
>                 Key: CONTINUUM-566
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-566
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.0.2
>            Reporter: Bob Herrmann
>         Attachments: add-build-number-to-mail-subject.diff
>
>
> Without a build number (and a sub-build number for failures - or repeat attempts) matching an email to a generated failure report is extremely difficult.   For example, when using a ant project a with the junit-report tag, junit generates a complete listing of all failed unit tests per test run.  With out a build number, matching a generated junit-report to a notification email is very difficult.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira