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

New namespace for Maven ecosystem proposal #106

Closed
skhokhlov opened this issue Nov 7, 2024 · 2 comments · Fixed by #107
Closed

New namespace for Maven ecosystem proposal #106

skhokhlov opened this issue Nov 7, 2024 · 2 comments · Fixed by #107

Comments

@skhokhlov
Copy link
Member

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 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.

@jkowalleck
Copy link
Member

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
@jkowalleck
Copy link
Member

For example: project1:scopeA,project1:scopeB,project2:scopeA.

no need for comma separated. Better go with a multi-use.
see #107 (comment)

skhokhlov added a commit to skhokhlov/cyclonedx-property-taxonomy that referenced this issue Nov 21, 2024
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

Successfully merging a pull request may close this issue.

2 participants