We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In java's ecosystem, with maven as build tool.
when a project specify it depends on some libraries, those libraries can also depends on other libraries.
for example:
project P -> lib A -> lib B -> lib c
for project P, only lib A is called direct dependency, while B and C are called transitive dependencies.
and dependencies can have scope, for example a project P may depends on lib B, but only for running unit tests.
project P -> lib A \-> lib B(test scope)
what's the corresponding concepts in this spec ?
The text was updated successfully, but these errors were encountered:
For scoping, I believe you can use LifecycleScopedRelationship
https://spdx.github.io/spdx-spec/v3.0.1/model/Core/Classes/LifecycleScopedRelationship/
Sorry, something went wrong.
Transitive dependencies are handles by creating relationship between the dependent library and their dependencies.
ie:
project P -> lib A : P dependsOn A \-> lib B(test scope) : A dependsOn, scope=test B
No branches or pull requests
In java's ecosystem, with maven as build tool.
when a project specify it depends on some libraries, those libraries can also depends on other libraries.
for example:
project P -> lib A -> lib B -> lib c
for project P, only lib A is called direct dependency, while B and C are called transitive dependencies.
and dependencies can have scope, for example a project P may depends on lib B, but only for running unit tests.
what's the corresponding concepts in this spec ?
The text was updated successfully, but these errors were encountered: