Add a configuration option to skip undeployed artifacts

[ppkarwasz]

This adds a <skipNotDeployed> plugin configuration option. If set to false, even artifacts that do not have a deploy execution are used to generate the SBOM.

Closes #430

[bstrdsmkr]

+1 for this, it fixes a ton of our builds that were broken by the implementation of the previous feature

[hboutemy]

great job, thank you

[ankursharma180]

@hboutemy Thanks for this change, If you can provide some updates, when there will be a 2.7.11 release ?

[hboutemy]

there are 2 PRs I want to merge before doing the release: I hope we'll get that done soon

[ankursharma180]

Okay, thank you.
Really a great work. Thanks again. :-)
Waiting for this new release.

[olgti]

@ppkarwasz @hboutemy I'm executing mvn with this line: mvn org.cyclonedx:cyclonedx-maven-plugin:2.7.11:makeAggregateBom -DskipNotDeployed=false
However the project without deploy still being skipped: --- cyclonedx-maven-plugin:2.7.11:makeAggregateBom (default-cli) @ sfci-p2p ---
[INFO] Skipping CycloneDX goal, because module skips deploy
Any suggestions? Am I passing the param incorrectly? Thanks

[MukhachevDima]

@ppkarwasz @hboutemy I'm executing mvn with this line: mvn org.cyclonedx:cyclonedx-maven-plugin:2.7.11:makeAggregateBom -DskipNotDeployed=false However the project without deploy still being skipped: --- cyclonedx-maven-plugin:2.7.11:makeAggregateBom (default-cli) @ sfci-p2p --- [INFO] Skipping CycloneDX goal, because module skips deploy Any suggestions? Am I passing the param incorrectly? Thanks

Hello! Your problem is probably already resolved. But for anyone who has the same problem: you should run maven with arg -Dcyclonedx.skipNotDeployed=false. This helped me.