CycloneDX / CycloneDX/cyclonedx-maven-plugin
Sort by artifactId
- Dominant language
- Java
- Stars
- 385
- Forks
- 107
- Avg merge
- 17h 31m
- Merged PRs (30d)
- 7
Description
I'm a big fan of stable and easy to read output for any tool. Therefore I'd like to provide a patch which sorts the projects in the reactor by artifact id, before doing any further work. That would lead to the "excluded" or "analyzing" output to be sorted, and might also lead to a more stable order in the generated output files.
Right now, just changing module order in a reactor can lead to different output, although there hasn't been any semantic change from the dependency point of view.
Any concerns about that?
Contributor guide
Research direction
The issue names reactor project processing and the excluded/analyzing output, but no files or tests. Start by locating the entry point that processes reactor projects and trace where those outputs are assembled. Done means the processing and resulting output use artifactId order, with tests covering stable ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100