[
https://issues.apache.org/jira/browse/GROOVY-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977741#comment-14977741
]
John Wagenleitner commented on GROOVY-3963:
-------------------------------------------
The issue of script output being sent to multiple console windows should be
addressed with the fix for GROOVY-4888. Even though the title says {{windows
should be their own process}} it really seems like the main issue here was with
the output being directed to all console output areas.
If the issue is really about {{windows should be their own process}} then I
think the best way to achieve that is with the existing {{groovyConsole}}
command. The user can execute that script to create a new console window that
is a separate process. I think executing that should be left to the user and
not attempted from an existing jvm process.
> GroovyConsole windows should be their own process
> -------------------------------------------------
>
> Key: GROOVY-3963
> URL: https://issues.apache.org/jira/browse/GROOVY-3963
> Project: Groovy
> Issue Type: Bug
> Components: Groovy Console
> Affects Versions: 1.7.0
> Environment: Tested on Windows XP
> Reporter: Keegan Witt
> Priority: Minor
>
> The output is shared between GroovyConsole windows created from the same
> process, since requesting a new window doesn't create a new process.
> Steps to reproduce:
> 1. Open a new console window (ctrl + shift + n)
> 2. Cause some output to be generated
> 3. Observe output in original window
> The output of that script will be displayed on all console windows created in
> the (ctrl + shift + n) way but not when it is launched as a new process. I
> believe the latter behavior to be preferable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
