You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:23:24 UTC
[jira] (MPJUNITREPORT-1) junit/cactus error output should be
displayed in the report
[ https://jira.codehaus.org/browse/MPJUNITREPORT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MPJUNITREPORT-1.
--------------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> junit/cactus error output should be displayed in the report
> -----------------------------------------------------------
>
> Key: MPJUNITREPORT-1
> URL: https://jira.codehaus.org/browse/MPJUNITREPORT-1
> Project: Maven 1.x JUnit Report Plugin
> Issue Type: Bug
> Reporter: Daniel Rabe
> Priority: Minor
>
> -----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
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)