fernflower を Homebrew, dnf でインストール

プロジェクトリンク

• ホームページ
• 上流ドキュメント
• パッケージマネージャページ

コマンドとエイリアス

• fernflower

プロジェクトの歴史

Fernflower predates its current GitHub repository history: the README credits the original development to Stiver and says JetBrains has maintained it since 2014. The GitHub repository itself was created in October 2014 and points to the IntelliJ Community repository as the release location.

The project became part of the wider IntelliJ Java tooling stack rather than a standalone decompiler-only product. Its repository README tells contributors to send patches through the IntelliJ Community project, and its issue tracker route is the IntelliJ IDEA `Java. Decompiler. Engine` subsystem.

採用の歴史

Fernflower's main adoption channel is IntelliJ IDEA, where it is bundled for class-file navigation and debugging. Package-manager adoption gives command-line users a standalone `fernflower` executable or wrapper without needing to extract the engine from an IDE installation.

The README also notes that patches from ForgeFlower were merged and that a long-running mirror by Andrew McRae existed, which reflects Fernflower's role in the broader Java reverse-engineering and Minecraft-modding adjacent decompiler ecosystem.

使われ方

Standalone usage runs `java -jar fernflower.jar` with options, one or more class/JAR/ZIP sources, and an output destination. The documented options cover generic signatures, inner classes, synthetic members, lambda handling, identifier renaming, logging, line endings, indentation, and other decompiler behavior.

Inside IntelliJ IDEA, Fernflower is used implicitly when a developer opens or debugs against compiled Java classes without source attached. That dual IDE-and-CLI role is why it is useful both to Java developers and to package users who want scriptable decompilation.

パッケージ好きにとっての重要性

Fernflower matters in package culture because it packages a decompiler engine from a large IDE ecosystem into a small command-line tool. It also sits at an interesting boundary: official releases are tied to JetBrains' IntelliJ infrastructure, while downstream package managers expose it as a normal CLI.

For Java tooling maintainers, it is a notable example of an IDE component with standalone utility, Apache-licensed source, and ongoing relevance as Java bytecode features evolve.

タイムライン

• 2014: JetBrains begins maintaining Fernflower and the public GitHub repository is created.
• 2014 onward: Fernflower is maintained as part of the IntelliJ Java decompiler engine.
• 2026: GitHub repository metadata shows continuing updates.

Related projects

• Fernflower is related to IntelliJ IDEA, the IntelliJ Community repository, ForgeFlower, and the wider family of Java bytecode decompilers used by developers and reverse engineers.

ソース

• https://github.com/JetBrains/fernflower
• https://github.com/JetBrains/fernflower/blob/master/README.md
• https://api.github.com/repos/JetBrains/fernflower
• https://formulae.brew.sh/formula/fernflower