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

Make it possible to automatically determine components to analyse by reading source code #171

Open
goldmann opened this issue Jan 4, 2023 · 0 comments

Comments

@goldmann
Copy link

goldmann commented Jan 4, 2023

One option to run the analysis with domino is to provide a configuration file. Example can be found below:

{
  "project-bom": "org.bf2:kas-fleetshard:0.30.1-SNAPSHOT",
  "include-non-managed": true,
  "exclude-parent-poms": true,
  "project-artifacts": [
    "org.bf2:kas-fleetshard-api:0.30.1-SNAPSHOT",
    "org.bf2:kas-fleetshard-common:0.30.1-SNAPSHOT",
    "org.bf2:kas-fleetshard-operator:0.30.1-SNAPSHOT",
    "org.bf2:kas-fleetshard-sync:0.30.1-SNAPSHOT"
  ],
  "include-artifacts": [],
  "include-patterns": [],
  "exclude-patterns": [],
  "exclude-bom-imports": true,
  "level": -1,
  "log-artifacts-to-build": true,
  "log-modules-to-build": false,
  "log-trees": false,
  "log-remaining": false,
  "log-summary": true,
  "log-code-repos": false,
  "log-code-repo-tree": false,
  "validate-code-repo-tags": false,
  "warn-on-resolution-errors": false,
  "include-already-built": false,
  "log-non-managed-visitied": true
}

It would be great to have an option to point it to a directory where the source code is located as well. The tool would read the project and determine which components should be investigated. This should work for Maven and Gradle projects ideally.

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

1 participant