Michael Osipov created MNG-8017:
-----------------------------------

             Summary: Maven fails at start with "Cannot run program "infocmp": 
error=2, No such file or directory"
                 Key: MNG-8017
                 URL: https://issues.apache.org/jira/browse/MNG-8017
             Project: Maven
          Issue Type: Bug
          Components: Command Line
    Affects Versions: 4.0.0-alpha-13
         Environment: Apache Maven 4.0.0-alpha-13-SNAPSHOT 
(7f70467aa3e74a9bba602e5c61a0b5d33ae8f699)
Maven home: /usr/home/mosipov/var/Projekte/apache-maven-4.0.0-alpha-13-SNAPSHOT
Java version: 1.8.0_382, vendor: OpenJDK BSD Porting Team, runtime: 
/usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "13.2-release-p8", arch: "amd64", family: "unix"
            Reporter: Michael Osipov


>From {{mvn -v}}:
{noformat}
mosipov@bsd1srv:/usr/home/mosipov/var/Projekte/maven (master =)
$ ../apache-maven-4.0.0-alpha-13-SNAPSHOT/bin/mvn -v
Jan 14, 2024 9:30:35 PM org.jline.utils.Log logr
WARNUNG: Unable to retrieve infocmp for type xterm-color
java.io.IOException: Cannot run program "infocmp": error=2, No such file or 
directory
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
        at org.jline.utils.InfoCmp.getInfoCmp(InfoCmp.java:544)
        at 
org.jline.terminal.impl.AbstractTerminal.parseInfoCmp(AbstractTerminal.java:207)
        at 
org.jline.terminal.impl.PosixSysTerminal.<init>(PosixSysTerminal.java:47)
        at 
org.jline.terminal.impl.exec.ExecTerminalProvider.posixSysTerminal(ExecTerminalProvider.java:100)
        at 
org.jline.terminal.impl.exec.ExecTerminalProvider.sysTerminal(ExecTerminalProvider.java:66)
        at org.jline.terminal.TerminalBuilder.doBuild(TerminalBuilder.java:428)
        at org.jline.terminal.TerminalBuilder.build(TerminalBuilder.java:362)
        at 
org.apache.maven.cli.jline.MessageUtils.systemInstall(MessageUtils.java:47)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: java.io.IOException: error=2, No such file or directory
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:251)
        at java.lang.ProcessImpl.start(ProcessImpl.java:134)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
        ... 17 more

Apache Maven 4.0.0-alpha-13-SNAPSHOT (7f70467aa3e74a9bba602e5c61a0b5d33ae8f699)
Maven home: /usr/home/mosipov/var/Projekte/apache-maven-4.0.0-alpha-13-SNAPSHOT
Java version: 1.8.0_382, vendor: OpenJDK BSD Porting Team, runtime: 
/usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "13.2-release-p8", arch: "amd64", family: "unix"
{noformat}

There is no {{infocmp}} on FreeBSD.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to