Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error is reported when running under windows, the result shows only the first-level dependencies, and the reference dependency analysis fails #1076

Open
tiandiyixian opened this issue Oct 15, 2022 · 1 comment

Comments

@tiandiyixian
Copy link

tiandiyixian commented Oct 15, 2022

When I run the program, I find that the result under linux is correct, but the result of running under windows can only analyze the direct dependency, and the indirect dependency analysis fails. I changed several other windows machines and other versions of the fossa client ( 3.X), and even let other work colleagues try it, I found that the error content is the same, the project can be built successfully through maven, run mvn dependency:tree -DoutputType=dot -DoutputFile=./depend.dot alone The --fail-at-end command is also fine. This is the error log message:
[DEBUG] ----------
A task succeeded with 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

    Command execution failed:
        command: Command {cmdName = "mvn", cmdArgs = ["org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install-file","-DgroupId=com.github.ferstl", "-DartifactId=depgraph-maven-plugin","-Dversion=4.0.1","-Dpackaging=jar","-Dfile=C:\\Users\\demo\\AppData\\Local\\Temp\\ fossa-maven-b5823c40916d1c90\\plugin.jar"], cmdAllowErr = Never}
        dir: I:\yisuo202209\fossa_3.4.7_windows_amd64\java-sec-code-master\
        exit: ExitFailure 1
        stdout:

        stderr:
          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'
      -Installing plugin
      - Plugin analysis
      - Dynamic Analysis
      - Maven
      - Project Analysis: MavenProjectType

  Error

    Error reading file C:\Users\demo\AppData\Local\Temp\fossa-deptree-2484092621727851740.dot:
        C:\Users\demo\AppData\Local\Temp\fossa-deptree-2484092621727851740.dot: openBinaryFile: does not exist (No such file or directory)

    Traceback:
      - Parsing file 'C:\Users\demo\AppData\Local\Temp\fossa-deptree-2484092621727851740.dot'
      -Parsing 'mvn dependency:tree' output
      -Dynamic analysis
      - Dynamic Analysis
      - Maven
      - Project Analysis: MavenProjectType

  Error

    Command execution failed:
        command: Command {cmdName = "mvn", cmdArgs = ["org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install-file","-DgroupId=com.github.ferstl", "-DartifactId=depgraph-maven-plugin","-Dversion=3.3.0","-Dpackaging=jar","-Dfile=C:\\Users\\demo\\AppData\\Local\\Temp\\ fossa-maven-c003f3c6a2239687\\plugin.jar"], cmdAllowErr = Never}
        dir: I:\yisuo202209\fossa_3.4.7_windows_amd64\java-sec-code-master\
        exit: ExitFailure 1
        stdout:

        stderr:
          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'
      -Installing plugin
      - Legacy Plugin analysis
      - Dynamic Analysis
      - Maven
      - Project Analysis: MavenProjectType

The system runs in the windows10 environment,I think it may be because the analysis of dependencies failed, and the direct dependencies obtained by analyzing the pom.xml file were directly analyzed.I have used some other projects from github, the error content is the same, should it have nothing to do with the project.

@bill0cypher
Copy link

@tiandiyixian , I've had the same issue, the problem can be JDK version. Maven 3.6.x doesn't work properly with 17. Hence, try to downgrade to 11. Afterward, problem with plugins installation should be gone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants