Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Class decompiler doesn't use the contributed decompiler #3012

Closed
fbricon opened this issue Mar 21, 2023 · 0 comments · Fixed by eclipse-jdtls/eclipse.jdt.ls#2578
Closed

Class decompiler doesn't use the contributed decompiler #3012

fbricon opened this issue Mar 21, 2023 · 0 comments · Fixed by eclipse-jdtls/eclipse.jdt.ls#2578
Assignees
@JessicaJHee
Labels
bug decompile
Milestone
Mid April 2023

Comments

@fbricon
Copy link
Collaborator

fbricon commented Mar 21, 2023

Following on #2985, when opening a random .class, the internal disassembler is always used, ignoring the configured decompiler.

Steps To Reproduce
  1. Download, unzip and opened this inconsistent-decompiler.zip
  2. Make sure the "dgileadi.java-decompiler" extension is installed.
  3. Open src/foo/Bar.java
  4. Ctrl+Click on BouncyCastleProvider, the source was generated by the Fernflower decompiler
  5. Open bin/XMLServerLauncher.class
Current Result

The XMLServerLauncher source is generated by the JDT disassembler, instead of fernflower, so only contains stub methods

Expected Result

The XMLServerLauncher source should be generated by the configured "java.contentProvider.preferred" decompiler, fernflower in this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JessicaJHee JessicaJHee

Labels
bug decompile
Projects
IDE Cloudaptors
Archived in project
Milestone
Mid April 2023
Development

Successfully merging a pull request may close this issue.

Use contributed decompiler when opening class files JessicaJHee/eclipse.jdt.ls
3 participants
@fbricon @rgrunber @JessicaJHee