Try putting
maven.junit.usefile=false
in ~/build.properties (or project.properties). That tells it to stop
writing those .txt files and show them on the console instead.
On Thu, 2004-01-08 at 18:54, korosh afshar wrote:
> > korosh afshar wrote:
> >
> > > Sorry, I figured this out by looking at test-reports directory and saw a
> > > *.txt file there for the test failure message and stack trace.
> > >
> > >
> > > where do I look to change this junit configuration in merlin to spit out
> > > the message in console instead of the log file ?
> >
> > create a file called merlin.properties in the ${basedir} and add the
> > following properties:
> >
> > merlin.info = true
> > merlin.debug = true
>
>
> that didn't do it for me.
>
>
> I did find out after reading through more of maven documentation, that
> when I run maven with the test:single target giving it -Dtestcase
> argument, then the failure message shows up in the console upon
> assertion failure.
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
