-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
New namespace for Maven ecosystem proposal #106
Comments
fantastic please open the respective pull request(s) here and add whatever you need :D |
skhokhlov
added a commit
to skhokhlov/cyclonedx-property-taxonomy
that referenced
this issue
Nov 7, 2024
Signed-off-by: skhokhlov <[email protected]>
no need for comma separated. Better go with a multi-use. |
skhokhlov
added a commit
to skhokhlov/cyclonedx-property-taxonomy
that referenced
this issue
Nov 21, 2024
Signed-off-by: skhokhlov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm looking for populating component usage conditions for Maven (CycloneDX/cyclonedx-maven-plugin#505) and Gradle (CycloneDX/cyclonedx-gradle-plugin#440) plugins.
cdx:maven:package:test
First thing is distinguishing test and runtime components. This property can be
true
orfalse
. For Maven it means that the component is used only withintest
scope. For Gradle it means that component is used intest
configurations only.cdx:maven:package:projectsAndScopes
Second thing is linking components with projects (or subprojects) and scopes (or configurations in Gradle terms). It will help identify exact location in the project where component is used. This property contains comma separated list of pairs of project and configuration names. In case if component is used in multiply scopes for a project, dedicated pair will be used for it. For example:
project1:scopeA,project1:scopeB,project2:scopeA
.The text was updated successfully, but these errors were encountered: