[
https://issues.apache.org/jira/browse/MNG-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8582:
---------------------------------
Description: in mvnsh (and resident mvn), after mvn was invoked, the
stdout/stderr are "looped", writing to any of those causes SO. mvn and mvnd are
not affected, as former is "one off" (jvm exits), while in case of mvnd, it
installs own transport for stdout/stderr. (was: in mvnsh (and resident mvn),
after mvn was invoked, the stdout/stderr are "looped", writing to any of those
causes SO. mvn and mvnd are not involved, as former is "one off" (jvm exits),
while in case of mvnd, it installs own transport for stdout/stderr.)
> mvnsh sysout and syserr are clogged after mvn invoked
> -----------------------------------------------------
>
> Key: MNG-8582
> URL: https://issues.apache.org/jira/browse/MNG-8582
> Project: Maven
> Issue Type: Bug
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Blocker
> Fix For: 4.0.0-rc-3
>
>
> in mvnsh (and resident mvn), after mvn was invoked, the stdout/stderr are
> "looped", writing to any of those causes SO. mvn and mvnd are not affected,
> as former is "one off" (jvm exits), while in case of mvnd, it installs own
> transport for stdout/stderr.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
