Repository navigation
docs: explain how to identify JBang applications in VisualVM - #2697
gelatoni-xh wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Document VisualVM launch instructions docs/modules/ROOT/pages/running.adoc |
The guide describes setting visualvm.display.name at launch and finding the named application under VisualVM’s Local Applications. It also explains how to apply the option to a JAR file. |
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Merge Risk: 
34dee
-
The guide explains how to name a JBang application for VisualVM. No actionable issue remains before merge.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the main documentation change: explaining how to identify JBang applications in VisualVM. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Add a VisualVM section to the Running guide, next to the existing JVM diagnostics guidance. It shows how to pass
visualvm.display.namewithjbang runto identify the application, and notes that the same option works for JAR files.Refs #2639.
Validation:
jcmd.git diff --checkpasses.The VisualVM GUI display and full Antora site build have not been verified. This is a documentation-only change; the full Java build/test suite was not run.
Prepared with AI assistance; reviewed and approved for submission by the contributor.
Summary by CodeRabbit
visualvm.display.nameoption and explains how to apply it when launching either Java source files or JAR files.