HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
JetBrains
intellij-community
Java2013–2026
JetBrains / intellij-community

intellij-community

IntelliJ IDEA & IntelliJ Platform

64Distinct people
97Mentions
0Explicit recommenders
20.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

IntelliJ IDEA & IntelliJ Platform

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year97 dated mentions

Observed mentions: 2013-09-24 19:35:40 UTC to 2026-11-01 10:41:42 UTC.

0510152013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC514
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC202
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC505
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC817
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC505
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC13013
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC808
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC12012
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC10010
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC606
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC11011
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC716

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
IntelliJ Open Source Repository This repository is the open-source part of the JetBrains IDEs codebase. It also serves as the basis for IntelliJ Platform development. These instructions will help you build and run open source parts of IntelliJ Platform / IntelliJ IDEA / PyCharm. If you are new to the community and would like to contribute code or help others learn, see CONTRIBUTING.md to get started. The following conventions will be used to refer to directories on your machine: <USER_HOME> is your OS user's home directory. <IDEA_HOME> is the root directory for the IntelliJ source code. Getting the Source Code This section will guide you through getting the project sources and help avoid common issues in Git config and other steps before opening it in the IDE. Prerequisites Install Git. On Windows, set these Git options to avoid common issues during cloning: git config --global core.longpaths true git config --global core.autocrlf input Clone Main Repository IntelliJ open source repository is available from the GitHub repository, which can be cloned or downloaded as a zip file (based on a branch) into <IDEA_HOME>. The master (default) branch contains the source code which will be used to create the next major version of all JetBrains IDEs. The branch names and build numbers for older releases of JetBrains IDEs can be found on the Build Number Ranges page. You can clone this project using IntelliJ IDEA (see Opening the IntelliJ IDEA Source Code in the IDE). Alternatively, run the following commands in the terminal: git clone https://github.com/JetBrains/intellij-community.git cd intellij-community Tip For faster download: If the complete repository history isn't needed, create shallow clone. To download only the latest revision of the repository, add --depth 1 option after clone. Cloning in IntelliJ IDEA also supports creating shallow clone. Get Android Modules IntelliJ IDEA requires additional Android modules from separate Git repositories. Run the following script from project root <IDEA_HOME> to get the required modules: Unix: ./getPlugins.sh Windows: getPlugins.bat Important Always git checkout the intellij-community and android Git repositories to the same branches/tags. Building IntelliJ IDEA These instructions will help you build IntelliJ IDEA from source code, which is the basis for IntelliJ Platform development. Important IntelliJ IDEA project is currently being migrated to the Bazel build system. The migration is still in progress, so you may encounter some rough edges or temporary issues along the way, mostly related to IDE integration. Building the project using only IDE built-in capabilities is not supported anymore, so make sure the Bazel plugin is installed and enabled. Known issue: some tests are not yet possible to be run with Bazel. In case of any issues, please depend on the tests.cmd script mentioned in the Running IntelliJ IDEA in a CI/CD environment section. Opening the IntelliJ IDEA Source Code in the IDE Prerequisites: Install IntelliJ IDEA 2026.1 or newer. Install the Bazel plugin (via Settings | Plugins | Marketplace). If the Maven plugin is disabled, add the path variable MAVEN_REPOSITORY pointing to <USER_HOME>/.m2/repository directory. Using the latest IntelliJ IDEA, click File | Open and select the <IDEA_HOME>/.bazelproject. If IntelliJ IDEA displays a message about a missing or out-of-date required plugin (e.g., Kotlin), enable, upgrade, or install that plugin and restart IntelliJ IDEA. Building the IntelliJ IDEA Application In IntelliJ IDEA, choose Build | Build Project from the main menu. From the command line, run the bazel-build-all-community.cmd script in the <IDEA_HOME> directory (note: all *.cmd scripts work on both Windows and Unix systems). To build installation packages, run the installers.cmd script in the <IDEA_HOME> directory. Options to build installers are passed as system properties to installers.cmd command. You may find the list of available properties in BuildOptions.kt Pass --debug to suspend and wait for the debugger to attach to port 5005. Installer build examples: # Build installers only for current operating system: ./installers.cmd -Dintellij.build.target.os=current Tip The installers.cmd is used to run OpenSourceCommunityInstallersBuildTarget from the command line. You can also call it directly from IDEA, using run configuration Build IntelliJ IDEA Installers (current OS). Dockerized Build Environment To build installation packages inside a Docker container with preinstalled dependencies and tools, run the following command in <IDEA_HOME> directory (on Windows, use PowerShell): docker build . --target intellij_idea --tag intellij_idea_env docker run --rm --user "$(id -u)" --volume "${PWD}:/community" intellij_idea_env Note Please remember to specify the --user "$(id -u)" argument for the container's user to match the host's user. This prevents issues with permissions for the checked-out repository, the build output, if any. Running IntelliJ IDEA from IDEA To run the IntelliJ IDEA that was built from source, choose Run | Run... from the main menu and choose the preconfigured run configuration Run //build:idea_community. To run tests on the build, apply these settings to the Run | Edit Configurations... | Templates | JUnit configuration tab: Working dir: <IDEA_HOME>/bin VM options: -ea Running IntelliJ IDEA from the command line ./bazel.cmd run //build:idea_community Running IntelliJ IDEA in a CI/CD environment To run tests outside IntelliJ IDEA, use the tests.cmd command in <IDEA_HOME> directory. Options to run tests are passed as system properties to tests.cmd command. You may find the list of available properties in TestingOptions.kt # Run specific run configuration: ./tests.cmd -Dintellij.build.test.configurations=ApiCheckTest # Run a specific test: ./tests.cmd -Dintellij.build.test.patterns=com.intellij.util.ArrayUtilTest To debug tests, use: -Dintellij.build.test.debug.enabled=true -Dintellij.build.test
Read the full README on GitHub

What Hacker News says

5 sources
Java FX does look pretty, but the menu bar implementation is as broken as the one in Swing: * Switching to a different window with alt-tab will have moved keyboard focus to the menu bar when you switch back. * Holding down the mouse button, pointing at menus to open them and releasing to activate an item – the way people did it in ancient times and which has been supported everywhere forever – does not work. * To avoid submenus disappearing as you try to move the cursor towards them, GUI toolkits use either a small delay or something more clever to keep the submenu for a bit while you try to reach it. Except for Swing and JavaFX, which do neither, leading to a frustrating user experience. Interestingly, they have documented the correct behaviour in the JavaFX wiki[1], but it's apparently not implemented. (They had similar design documenta
Read the rest
tion on the Swing wiki, which I can't find now, which was also never implemented.) (The Swing menu bar is broken in many similar ways, but in case someone is wondering why it works in IntelliJ, they implemented[2] the expected behaviour themselves.) [1] https://wiki.openjdk.java.net/display/OpenJFX/Menu+User+Expe... [2] https://github.com/JetBrains/intellij-community/blob/master/...
In Java 11 released
> unlike Intellij, which sells its IDE The fancy version costs money, yes, but the community edition is free and Apache licensed. Here's the source code: https://github.com/JetBrains/intellij-community > is there another major cause for most of the world drifting to the inferior choice? I've used both Eclipse and IntelliJ, as well as JetBrain's "ReSharper" tool in Visual Studio, and while the UI is obviously different, and in some ways better, some ways worse than Eclipse, the actual functionality and feature set of IntelliJ is clearly superior to Eclipse, especially all the refactoring and code smell tools. The feature list is just incredible and constantly increasing: https://www.jetbrains.com/idea/whatsnew/ Also, IdeaVim is way superior to Eclim, if you care about Vim keybindings and modal editing.
In Goodbye to Eclipse – the end of an era as an Eclipse plugin developer
embed vim as their text editor Part of that problem is that a really good IDE isn't editing text: it's editing code. One may retort "but code is stored in text files," and yes, that happens to be the primary serialization format but while it's in RAM the editor is making changes to the AST (for example)[1] and the MPS project[2] even strives to do away with "text file" façade entirely, allowing you to edit the parts that are truly editable, and just graphically render the syntatic sugar for everything else. That distinction is relevant to the question because merely embedding vim would be problematic since the common language spoken between the IDE's mental model and vim's mental model is text, but I couldn't imagine the pain that would be involved in trying to send down the keystrokes required to update all occurrences of a variable, for
Read the rest
example. IntelliJ does have emacs bindings, and does have a vim plugin, but I've watched people use both of them and they suffer from the uncanny valley effect. Not to mention the fact that, and I can't stress this enough, entering character level keyboard shortcuts to change an AST is optimizing the wrong problem. that can do something like that is emacs I've actually spent many, many hours thinking about that very issue, and I am 100% convinced in my soul that a sufficiently determined person could in fact make Emacs as smart as IntelliJ. But the problem isn't making it that smart, it's keeping it up to date with the new bugfixes and rules. It might be possible (heh, or even preferable!) to write the AST manipulation and inspection rules using (e)lisp, but given how many developers know Java versus how many know lisps, I doubt a commercial company would bet the farm on such a thing. --- 1 = https://github.com/JetBrains/intellij-community/blob/idea/17... 2 = https://github.com/JetBrains/MPS/tree/2017.3.2#jetbrains-mps
In Frontmacs

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.