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

Maven analysis unable to deal with non unique artifactIds in different groupIds #1045

Open
FaIng95 opened this issue Aug 6, 2024 · 0 comments

Comments

@FaIng95
Copy link

FaIng95 commented Aug 6, 2024

We use the licenseFinder to analyze Maven projects which also contain many of our own dependencies.

The dependency_decisions.yml seems to only allow maven dependencies defined by their ArtifactId, which is not a unique identifier and therefore leads to wrong reporting of assigned licenses.

See the following very simple example with two artifacts with same artifactId (and different groupIds - so maven build itself works fine):

- - :license
  - calculation-api
  - some Other license
  - :who: me
    :why: the license is misspelled in the library
    :versions: []

- - :license
  - calculation-api
  - ourOwnLicense
  - :who: me
    :why: its our own internal artifact
    :versions: []

There should be a way to add the groupId to the dependency_decision.yml for unique identification.

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