-
Notifications
You must be signed in to change notification settings - Fork 314
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
analyzer: Empty binaryRemoteArtifact for Gradle project's dependency causes duplicate package error and prohibits result file creation #6780
Comments
Thanks for the reproducer! I can confirm the issue on |
Oh, sounds interesting! |
I tried this |
No, but you need to explicitly enable |
@sschuberth I am trying to run locally using this instruction. I tried modifying ~/.ort/config/config.yaml and through command-line, but new package manager somehow is not found. Am I missing something? I did git pull today and I assume the code is already merged. The run configuration looks like this: Maybe you have some idea or hint why GradleInspector package manager could not be found? |
@sschuberth the extension was correct, I quoted it in incorrectly. Restarting IDE and rerunning Gradle sync multiple times apparently helped and it's visible now. Easy way to prove that it's IDE issue is to check source tree: I checked and now combination Maven+GradleInspector works fine on my example. Should I close this issue? |
If the current implementation works for you, then yes, please go ahead. For "real" cases of "packages and projects with the same ids" we already have #6465. |
Yes, #6465 is the one I observe now again. Back to different binary/source URLs topic caused by artifactory mirrors :) |
enabledPackageManagers: [Maven, Gradle]
)Something causes binaryArtifact to be empty in Gradle project, which in turn causes two entries in Set where only binaryArtifact differs (empty and non-empty).
This in turn creates duplicate packages error, e.g.:
To simplify debugging, I've create a test project where issue is reproducible with current HEAD and the issue above is visible:
https://github.com/devcooch/ort-gradle-maven-issue
The text was updated successfully, but these errors were encountered: