sentry-cli bundle-jvm collects JVM sources from project roots

Introduced 2026-04-20 · score 0.97

HOW TO USE IT

When bundling JVM sources from a project root, run `sentry-cli debug-files bundle-jvm` with the required input directory, output directory, and debug UUID; repeat `--exclude` for custom glob patterns. The v3.4.0 source also collects extensions beyond those listed in the release note, so the supported extension set is not fully documented here.

WHY THIS HELPS

Bundle JVM sources from a project root, including a multi-module repository, while excluding files or directories that match custom glob patterns.

BEFORE THIS CHANGE

Do not run `bundle-jvm` directly on a project root.

REQUIREMENTS AND LIMITATIONS

• Version: 3.4.0
• PATH (required): Directory containing source files to bundle.
• --output PATH (required): Output folder; command writes a ZIP named with the debug UUID.
• --debug-id UUID (required): Debug ID used for the source bundle.
• --exclude PATTERN: Glob pattern for files/directories to exclude; can be repeated.
• Prerequisite: Use sentry-cli version 3.4.0 or later for the project-root collection and `--exclude` changes.
• Prerequisite: The input path must exist and be a directory.
• Automatic collection is limited to JVM source files with the listed extensions.
• The collection respects `.gitignore` and excludes common build output directories.
• Docs conflict: The release note lists `.java`, `.kt`, `.scala`, and `.groovy`; the v3.4.0 source's extension list additionally includes `.sc`, `.gvy`, `.gy`, `.gsh`, `.clj`, and `.cljc`. This difference is not used to override the release note.

FIRST-PARTY EVIDENCE

• https://github.com/getsentry/sentry-cli/releases/tag/3.4.0
• https://raw.githubusercontent.com/getsentry/sentry-cli/3.4.0/src/commands/debug_files/bundle_jvm.rs

Check the installed version and the source before using it. Entry JSON

Report a problem with this card