[
https://issues.apache.org/jira/browse/MSHARED-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720347#comment-17720347
]
ASF GitHub Bot commented on MSHARED-1072:
-----------------------------------------
slawekjaranowski commented on PR #140:
URL:
https://github.com/apache/maven-shared-utils/pull/140#issuecomment-1537512937
> Does this always apply? Are there cases were in the stream is not `stdin`?
It will be safer to use non blocking io in such case.
Even when stream will be not System.in it will work.
We also can not close provided stream because can be used for multiple
executing of invoker.
> executeCommandLineAsCallable hangs forever if InputStream is used
> -----------------------------------------------------------------
>
> Key: MSHARED-1072
> URL: https://issues.apache.org/jira/browse/MSHARED-1072
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-shared-utils
> Affects Versions: maven-shared-utils-3.4.1
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: maven-shared-utils-3.4.0, maven-shared-utils-3.4.1
>
>
> When we use method {{executeCommandLineAsCallable}} and provide InputSteam as
> systemIn, after process is finished method wait forever until InputStream
> will be closed.
> When we provide System.in as parameter InputStream will be not closed until
> process finished.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
