You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "velo (via GitHub)" <gi...@apache.org> on 2023/02/15 01:43:29 UTC
[GitHub] [maven-mvnd] velo commented on issue #786: Regression "WARNING: Unable to create a system terminal, creating a dumb terminal"
velo commented on issue #786:
URL: https://github.com/apache/maven-mvnd/issues/786#issuecomment-1430632964
Hi @gnodet
Here goes the output on 0.8.2 (which works) and 0.9.0 (which does not)
```
$ MVND_CLIENT=jvm MAVEN_OPTS="-DconsoleLevel=debug" ./mvnd.cmd -v
Picked up _JAVA_OPTIONS: -Duser.home=H:\Documents
851 DEBUG o.m.mvnd.client.DefaultClient - Starting client
Looking up daemon... time: 00:00nRegistry - loading own PID from VM name: 17620
1344 DEBUG o.m.mvnd.client.DaemonConnector - Found 1 idle daemons, 1 compatibles
1344 DEBUG o.m.mvnd.client.DaemonConnector - Connecting to Daemon
1346 DEBUG o.m.mvnd.client.DaemonConnector - Trying to connect to address /127.0.0.1:59250.
1366 DEBUG o.m.mvnd.client.DaemonConnector - Connected to address /127.0.0.1:59250.
1366 DEBUG o.m.mvnd.client.DaemonConnector - Exchanged token successfully
1527 DEBUG o.m.mvnd.client.DaemonConnector - Connected
mvnd 0.8.2 JVM client (2bba2d6a4d3a5012ddf9f1f42a22784cad4011e3)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.ExecPty
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: C:\Program Files (x86)\Development\mvnd-0.8.0-windows-amd64\mvn
Java version: 17.0.4, vendor: Oracle Corporation, runtime: C:\Program Files (x86)\Development\SDKs\jdk-17.0.4
Default locale: en_NZ, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
1761 DEBUG o.m.m.client.DaemonClientConnection - thread 1: connection stop
```
```
$ MVND_CLIENT=jvm MAVEN_OPTS="-DconsoleLevel=debug" ./mvnd.sh -v
Picked up _JAVA_OPTIONS: -Duser.home=H:\Documents
1337 DEBUG o.m.mvnd.client.DefaultClient - Starting client
Looking up daemon... time: 00:01nRegistry - loading own PID from VM name: 19448
1873 DEBUG o.m.mvnd.client.DaemonConnector - Found 0 idle daemons, 0 compatibles
1874 DEBUG o.m.mvnd.client.DaemonConnector - Found 0 busy daemons, 0 cancelled, 0 compatibles
Starting new daemon 516bea0e (subsequent builds will be faster)... time: 00:01
1998 DEBUG o.m.mvnd.client.DaemonConnector - Starting daemon process: id = 516bea0e, workingDir = C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\bin, daemonArgs: C:\Program Files (x86)\Development\SDKs\jdk-17.0.4\bin\java.exe -classpath C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\lib\mvnd-common-0.9.0.jar;C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\lib\mvnd-agent-0.9.0.jar -javaagent:C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\lib\mvnd-agent-0.9.0.jar -Dmvnd.home=C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64 -Dmaven.home=C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64 -Dmaven.conf=C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\conf -Dmvnd.java.home=C:\Program Files (x86)\Development\SDKs\jdk-17.0.4 -Dlogback.configurationFile=C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64\conf\logging\logback-mvnd.xml -Dmvnd.id=516bea0e -
Dmvnd.daemonStorage=H:\Documents\.m2\mvnd\registry\0.9.0 -Dmvnd.registry=H:\Documents\.m2\mvnd\registry\0.9.0\registry.bin -Dmvnd.socketFamily=inet -Dmvnd.home=C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64 -Djdk.java.options=--add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED --add-opens java.base/sun.nio.fs=ALL-UNNAMED -Dmvnd.noDaemon=false -Dmvnd.debug=false -Dmvnd.debug.address=8000 -Dmvnd.idleTimeout=3h -Dmvnd.keepAlive=100ms -Dmvnd.extClasspath= -Dmvnd.coreExtensions= -Dmvnd.enableAssertions=false -Dmvnd.expirationCheckDelay=10s -Dmvnd.duplicateDaemonGracePeriod=10s -Dmvnd.socketFamily=inet org.mvndaemon.mvnd.common.MavenDaemon
2066 DEBUG o.m.mvnd.client.DaemonConnector - Started Maven daemon 516bea0e
4105 DEBUG o.m.mvnd.client.DaemonConnector - Connecting to Daemon
4105 DEBUG o.m.mvnd.client.DaemonConnector - Trying to connect to address /127.0.0.1:54419.
4135 DEBUG o.m.mvnd.client.DaemonConnector - Connected to address /127.0.0.1:54419.
4136 DEBUG o.m.mvnd.client.DaemonConnector - Exchanged token successfully
4331 DEBUG o.m.mvnd.client.DaemonConnector - Connected
Apache Maven Daemon (mvnd) 0.9.0 JVM client (fa3cc5d66458a8526bd543de85566293113dacc4)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.ExecPty
Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
Maven home: C:\Program Files (x86)\Development\maven-mvnd-0.9.0-windows-amd64
Java version: 17.0.4, vendor: Oracle Corporation, runtime: C:\Program Files (x86)\Development\SDKs\jdk-17.0.4
Default locale: en_NZ, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
4624 DEBUG o.m.m.client.DaemonClientConnection - thread 1: connection stop
```
Noticed that by adding `MVND_CLIENT=jvm` I get the nice output, w/o it I get `mvn` style output.
Sadly, just adding consoleLevel debug doesn't produce any output
```
$ MAVEN_OPTS="-DconsoleLevel=debug" "/c/Program Files (x86)/Development/maven-mvnd-0.9.0-windows-amd64/bin/mvnd.sh" Feb 15, 2023 2:36:58 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
```
Also, forgot to mention on the original PR, I'm using mintty/git bash as terminal.
Cheers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org