Document how to scan Java JAR directories with SCA#36997
Merged
Conversation
Adds a new Scan Java JAR directories subsection under the CI pipelines section for Java projects that check third-party JARs into the repo instead of relying on Maven or Gradle manifests. Documents the opt-in JAR parser in datadog-sbom-generator >= 1.10.2, including requirements, enabling the parser, uploading the SBOM, component identification, and limitations. Also adds a one-line cross-reference under the supported-manifests table so customers with custom Java builds can find the new section. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
The JAR directory scanning feature is a niche use case for Java projects with custom build systems. Moving the full documentation to the troubleshooting page reduces its prominence in the main setup flow while keeping it discoverable. The setup page now has a single-line cross-reference under the Scan in CI pipelines section pointing to the troubleshooting page. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Created DOCS-14505 for the editorial review. |
drichards-87
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds documentation for scanning Java JAR directories with
datadog-sbom-generator.Some Java projects use custom build systems and check third-party JARs directly into the repository — typically into a
lib/directory — instead of relying on a complete Maven or Gradle manifest. For these projects, the JAR files on disk are the most reliable record of what the build actually depends on.This change adds a new Scan Java JAR directories subsection under the existing CI scanning guidance. It documents:
datadog-sbom-generator1.10.2 and later--enable-parsers jardatadog-cipom.propertiesmetadata.jaronlyThis change also adds a one-line cross-reference under the supported-manifests table so customers with custom Java builds can find the new section quickly.
.jaris intentionally not added to the manifests table — the JAR parser scans packaged binaries, not dependency manifests, and the distinction matters for choosing the right scan target.Merge instructions
Merge readiness:
Additional notes