[
http://jira.codehaus.org/browse/JBEHAVE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247362#action_247362
]
Paul Hammant commented on JBEHAVE-370:
--------------------------------------
Actually, it was strictly speaking not a bug. More an accident of having to
override stuff to get a custom StoryReporter in the mix (for WebDriver)
> IDE_CONSOLE no longer any different to IDE (w.r.t console output)
> -----------------------------------------------------------------
>
> Key: JBEHAVE-370
> URL: http://jira.codehaus.org/browse/JBEHAVE-370
> Project: JBehave
> Issue Type: Bug
> Affects Versions: 3.1
> Reporter: Paul Hammant
> Assignee: Paul Hammant
> Fix For: 3.2
>
>
> I've noticed recently a problem with IDE_CONSOLE. It (or more particularly
> the IdeOnlyConsoleOutput class) is being ignored. If you do a Maven run from
> the command line, for a project that uses a normal on JB3.1/JUnit tool chain
> you can see it.
> Put in a strategic throw, or loop/sys-out for the current threads stack
> trace, you don't have the prerequisite packages in the stack (I've checked),
> yet it still dump to console :-(
> Maybe there is a System.out somewhere that is ignore this configuration
> choice.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
