[
https://issues.apache.org/jira/browse/MNG-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907595#comment-17907595
]
Tamas Cservenak commented on MNG-8460:
--------------------------------------
What I have so far: Prompters do work if user specifies {{--raw-streams}} in
CLI.
But, this is wrong IMHO, as users should not do "extra switches" to make
Prompting work. Broader context is that {{--raw-streams}} was originally mvnd
parameters "ported to mvn"
(https://github.com/apache/maven/commit/740100b50c996f3e8b0823f53607c5acd283f133).
But the effect of it was this:
* this issue (Prompters)
* users also reported that {{mvn help:evaluate -Dexpression=xxx -DforceStdout}}
does not work without {{--raw-streams}}
I kinda feel like "raw-streams" option _default value_ should be different
between mvn and mvnd (unsure about the MT logging part)...
> All Prompter use seems busted
> -----------------------------
>
> Key: MNG-8460
> URL: https://issues.apache.org/jira/browse/MNG-8460
> Project: Maven
> Issue Type: Bug
> Reporter: Tamas Cservenak
> Priority: Blocker
> Fix For: 4.0.0-rc-3
>
>
> With current master (575ad3719c79b061c78d531ec9d29793f159c2ec) seems all
> prompter actions are defunct:
> * mvn release:prepare
> * mvn versions:set
> These all stalls forever (without any prompt/output) waiting for user
> input... something is borked.
> Prompt is not shown, but input is picked up. Still, this is bad, as user have
> no clue what the input should be.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
