feature: add the `lsp-java-bytecode-viewer` function.

Open
#493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
emacs-lisp, java
Domain
tooling

Research direction

Start by locating existing lsp-java commands and how they invoke jdtls. Read the jdtls support for the cfr, veinflower, and fernflower decompilers, then clarify how the current buffer should be passed to the viewer. Done means a new lsp-java-bytecode-viewer command can show the current buffer's bytecode or decompiled output.

Written by the indexing model from the issue text.

Description

The jdtls server itself contains cfr, veinflower and fernflower de-compilers.
It may be useful to add a new command to view the byte-code of current buffer.
The byte-code level viewer is useful for these cases:

  1. Debug the java source in the low-level.
  2. Write java codes for a java-agent, which requires to operate on the byte-code level.

This lsp-java-bytecode-viewer function can be done via calling the decompiler provided by jdtls.

Dominant language
Emacs Lisp
Stars
695
Forks
97
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from emacs-lsp/lsp-java

All issues in emacs-lsp/lsp-java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.