According to ZeroTurnaround’s RebelLabs’ “Java Tools and Technologies Landscape Report 2016” (https://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-2016-trends/), three players dominate the Java IDE market:

Each IDE has its fervent followers, so we want to tread carefully and not stir the pot!  The core CloudTurbine development team has its own favorite IDE – we’ve used Eclipse for years and happily continue to do so.  It offers solid performance and tools, including the Buildship plugin (which we regularly use for our Gradle builds).  But with IntelliJ IDEA dominating the market, I figured it was time to try this IDE out.

IntelliJ IDEA works great; it was easy to import our CloudTurbine “JavaCode” multi-project and run Gradle tasks in it.  From the initial “Welcome to IntelliJ IDEA” screen that pops up when the program starts, click on “Import Project”; in the file browser window that then pops up, select the “build.gradle” file from the JavaCode directory and click the OK button.  I kept the default import settings in the next dialog box that pops up.  All sub-projects (CTlib, CTstream, etc.) were automatically added in their own folder in the main IntelliJ IDEA user interface (see figure below).

A neat feature in IntelliJ is that it offers popup code completion for Gradle syntax when editing a Gradle script.  Android Studio is built on the IntelliJ platform, so IntelliJ IDEA is similar to Android Studio.  In fact, IDEA itself can open/build Android projects.  Thus, an advantage of IDEA is that this one IDE can be used to build all of the CloudTurbine projects (both “JavaCode” and “AndroidCode”).  Something that takes a little getting used to with IDEA is the auto-save feature.

I’m still an IntelliJ IDEA noob, and at this point there are things I like better about Eclipse.  But at least for a while I’ll continue to play with this powerful IDE!