[QUESTION] unable to select best binary to analyze project: none passed validation

[jiannanfan]

please give me some help, I can not fix this question by search.

project
spring boot/maven
no sub module

fossa config
depgraph-maven-plugin:4.0.1 is in the local maven repository
windows power shell
mvn commond is configed in the Path, maven's version is 3.6.3, and can excute mvn -v commond in the shell
no fossa.xml

here is the analyze summary
Scan Summary

fossa-cli version 3.8.22 (revision bcd1142 compiled with ghc-9.4)
fossa endpoint server version: 4.15.25

1 projects scanned; 0 skipped, 1 succeeded, 0 failed, 4 analysis warnings

• maven project in "D:\work\workspace5\xxx-cloud-service\": succeeded with 4 warnings

---

maven project in "D:\work\workspace5\xxx-cloud-service\": succeeded with 4 warnings

Warning

Could not analyze edges between dependencies.

Could not analyze deep dependencies.

Details

Failed to install maven plugin for analysis.

Failed to install maven plugin for analysis.

Relevant errors

Error

  unable to select best binary to analyze project: none passed validation

  Traceback:
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Installing plugin
    - Plugin analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

Error

  unable to select best binary to analyze project: none passed validation

  Traceback:
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Build maven command
    - Dynamic analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

Error

  unable to select best binary to analyze project: none passed validation

  Traceback:
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Installing plugin
    - Legacy Plugin analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

Warning

Command "mvn" not suitable: running with args ["-v"] resulted in a non-zero exit code

Relevant errors

Error

  Command execution failed: 

      Attempted to run the command 'mvn -v'
      inside the working directory 'D:\work\workspace5\xxx-cloud-service\',
      but failed, because the command exited with code '1'.

      Often, this kind of error is caused by the project not being ready to build;
      please ensure that the project at 'D:\work\workspace5\xxx-cloud-service\'
      builds successfully before running fossa.

      The logs for the command are listed below.
      They will likely provide guidance on how to resolve this error.
      Command did not write a standard log.

      Command error log:
        mvn: startProcess: does not exist (No such file or directory)

  If you believe this to be a defect, please report a bug to FOSSA support at https://support.fossa.com

  Traceback:
    - Running command 'mvn'
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Installing plugin
    - Legacy Plugin analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

Warning

Command "mvn" not suitable: running with args ["-v"] resulted in a non-zero exit code

Relevant errors

Error

  Command execution failed: 

      Attempted to run the command 'mvn -v'
      inside the working directory 'D:\work\workspace5\xxx-cloud-service\',
      but failed, because the command exited with code '1'.

      Often, this kind of error is caused by the project not being ready to build;
      please ensure that the project at 'D:\work\workspace5\xxx-cloud-service\'
      builds successfully before running fossa.

      The logs for the command are listed below.
      They will likely provide guidance on how to resolve this error.
      Command did not write a standard log.

      Command error log:
        mvn: startProcess: does not exist (No such file or directory)

  If you believe this to be a defect, please report a bug to FOSSA support at https://support.fossa.com

  Traceback:
    - Running command 'mvn'
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Build maven command
    - Dynamic analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

Warning

Command "mvn" not suitable: running with args ["-v"] resulted in a non-zero exit code

Relevant errors

Error

  Command execution failed: 

      Attempted to run the command 'mvn -v'
      inside the working directory 'D:\work\workspace5\xxx-cloud-service\',
      but failed, because the command exited with code '1'.

      Often, this kind of error is caused by the project not being ready to build;
      please ensure that the project at 'D:\work\workspace5\xxx-cloud-service\'
      builds successfully before running fossa.

      The logs for the command are listed below.
      They will likely provide guidance on how to resolve this error.
      Command did not write a standard log.

      Command error log:
        mvn: startProcess: does not exist (No such file or directory)

  If you believe this to be a defect, please report a bug to FOSSA support at https://support.fossa.com

  Traceback:
    - Running command 'mvn'
    - Evaluate command: mvn
    - Command override supported, but not specified
    - Make analysis command from CandidateAnalysisCommands {candidateCmdNames = "mvn" :| [], candidateCmdArgs = ["-v"], candidateOverrideKind = Just MavenType}
    - Installing plugin
    - Plugin analysis
    - Dynamic Analysis
    - Maven
    - Project Analysis: MavenProjectType

[github-actions]

Thank you @jiannanfan for creating this issue. If this is in regards to a defect, product question or feature request: you should use our support portal at https://support.fossa.com to file a request, as you would receive more immediate support.