First thing is distinguishing test and runtime components. This property can be true or false. For Maven it means that the component is used only within test scope. For Gradle it means that component is used in test 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.
I'm looking for populating component usage conditions for Maven (https://github.com/CycloneDX/cyclonedx-maven-plugin/issues/505) and Gradle (https://github.com/CycloneDX/cyclonedx-gradle-plugin/issues/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
.