You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/12/31 05:05:42 UTC

[jira] Commented: (MAVEN-1019) junit/cactus error output should be displayed in the report

The following comment has been added to this issue:

     Author: Brett Porter
    Created: Tue, 30 Dec 2003 10:05 PM
       Body:
it would be worth reporting this on Cactus' issue tracking too as this is now a separate plugin from Maven.
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1019


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1019
    Summary: junit/cactus error output should be displayed in the report
       Type: Bug

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Versions:
             1.0-rc1

   Assignee: 
   Reporter: Daniel Rabe

    Created: Mon, 10 Nov 2003 10:59 AM
    Updated: Tue, 30 Dec 2003 10:05 PM

Description:
-----Original Message-----
From: Vincent Massol [mailto:vmassol@pivolis.com] 
Sent: Saturday, November 08, 2003 5:45 AM
To: 'Maven Users List'
Cc: drabe@opentext.com
Subject: RE: Getting cactus error output into the report


Ok, I've had a better look. I was right. The cactus.jsl is an exact copy of the junit-report's junit.jsl file which does not display stack trace. So I'd say you should open a bug report against the junit-report plugin and I'll make sure that I update Cactus's cactus.jsl file.

Thanks
-Vincent

> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: 08 November 2003 12:27
> To: 'Maven Users List'
> Cc: drabe@opentext.com
> Subject: RE: Getting cactus error output into the report
> 
> Oops. Actually this may not be true. I had forgotten there was a 
> cactus.jsl file in the cactus plugin. I'll have a look and fix this.
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > Sent: 08 November 2003 11:56
> > To: 'Maven Users List'
> > Cc: drabe@opentext.com
> > Subject: RE: Getting cactus error output into the report
> >
> > Hi Daniel,
> >
> > It looks like it's a limitation of the Maven junit-report plugin.
> Could
> > you post a JIRA improvement report for the junit-report plugin.
> Although
> > I haven't tested it, I believe you'll also not see stack trace 
> > information for pure junit tests when using Maven.
> >
> > Thanks
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Daniel Rabe [mailto:drabe@opentext.com]
> > > Sent: 04 November 2003 01:34
> > > To: 'users@maven.apache.org'
> > > Subject: Getting cactus error output into the report
> > >
> > > I'm using maven with the cactus plugin on Windows XP. If one of my
> > cactus
> > > tests gets an error (it throws an exception), a stack trace is
> emitted
> > > into
> > > the .txt and .xml files in target/test-cactus-reports/tomcat5x.
> > However,
> > > the
> > > report that's generated by the cactus plugin only shows the
> exception
> > > message. It would really be helpful to have the actual stack trace
> in
> > the
> > > report. Is there any way I can configure maven and/or the cactus
> > plugin to
> > > do this?
> > >
> > > Thanks,
> > > Daniel Rabe



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org