The source code of the IntelliJ project was recently migrated to Java 17. We still have some modules compiled to be compatible with older Java versions so we can support running users’ projects under these versions. However, most of the platform and plugin modules now use Java 17, and the upcoming 2022.3 versions of all IntelliJ-based IDEs will require Java 17 to start. What does this mean for you? If you develop a plugin, you can use new language features and APIs from Java 17, but only if the since-build attribute in plugin.xml is set to 223. If your plugin distribution needs to run o

We've just pushed a major naming change to the IntelliJ codebase. For years, we hadn't set or followed any naming conventions for modules in the IntelliJ IDEA source, and things had gotten into a total mess (for example, we had a variety of names such as hg4idea, jetgroovy, ByteCodeViewer, testng_rt, and lang-impl). As usage of IntelliJ Platform grows, this has been causing more and more problems. So now we've finally put all names of modules in IntelliJ IDEA and IntelliJ Platform sources in order. This means that all 357 modules in the intellij-community project have been renamed. This

If you haven’t noticed yet, a fresh IntelliJ IDEA 14.1 EAP build is already available for download. In addition to bugfixes it also brings you enhanced Scratch Files feature. Scratch Files (Tools → New Scratch File) were introduced in IDEA 14.0 but now they become real files stored in IDE settings so they are shown in Project View, they survive IDE restarts and even can be executed: Get the new EAP build and share your feedback on our discussion forum or report any found bugs directly to the tracker.

Today we have published a new IDEA 14.1 EAP build. It fixes many bugs found in the first EAP build and also includes new features and improvements. In particular it supports automatic setup of GWT facets for projects imported from Gradle and allows you to view differences in a more compact form: If you experience any problems or want to suggest a new feature, feel free to write to our discussion forum or file issues directly to the issue tracker.

Since IntelliJ IDEA 11 the Mark Object action, which was previously available in JVM-based debuggers only, is also supported in JavaScript debuggers for Firefox and Chrome browsers. To mark an object press F11 on the corresponding node in any debugger tree and specify the label: After that the labeled object will be marked accordingly in all debugger views: By the way this feature also works in Flex debugger starting from IntelliJ IDEA 10.5.

Did you know what in IntelliJ IDEA 10.5 you can mark a directory as a Source Root or a Test Source Root right from the Project View? In IntelliJ IDEA 11 you also can create a library without opening the Project Structure dialog: just select jar files in the Project Structure and choose 'Add as Library...' in the context menu: The IDE will create a new library and will add it to the dependencies list of the selected module:

When you debug JavaScript code in IntelliJ IDEA 11 you can see the most important properties of an object without expanding its node: By default the 'id' and 'name' properties are shown for each object but you can add your own properties in Settings | Debugger | JavaScript: This feature works for both Firefox and Chrome JS debuggers. Let us know what you think!

Ultimate Edition of IntelliJ IDEA provides an additional way of inspecting the project structure — the diagram of module dependencies. To open it just press Ctrl+Alt+Shift+U or invoke Diagrams | Show Diagram from the context menu on a module node in Project View or Navigation Bar. IntelliJ IDEA 11 adds the ability to edit module dependencies using the diagram: press Delete on an edge to remove dependency or press Alt+Insert to add a new one. Your feedback is very welcome, as usual.

IntelliJ IDEA 10 allows you to debug JavaScript code running it in Mozilla Firefox. In IntelliJ IDEA 10.5 can choose to debug JavaScript in Google Chrome as well. Debugger for Chrome supports all features of JavaScript debugger for Firefox, you can set breakpoints, inspect local variables, evaluate expressions and so on: If you use Chrome for web browsing and want to debug in it simultaneously you can configure IntelliJ IDEA to use a separate Chrome user profile in 'IDE Settings | Browser | Chrome': To configure the default debugging browser just edit the 'JavaScript Debug' configurat

IntelliJ IDEA 10 includes an option to setup an application server right in the New Project Wizard. You only need to specify a directory where the server is installed: IntelliJ IDEA will create a sample application, setup it accordingly for the selected server and will add a corresponding Run Configuration. Once project is created you can just click Run button to start the server.

Since the last EAP build IntelliJ IDEA X provides an action to quickly create a single Jar artifact containing your modules with all dependencies. Just press '+' button in the Project Structure dialog and select the appropriate item: IntelliJ IDEA shows a dialog allowing you to customize the artifact: After that you can build the Jar file using Build | Build Artifact menu item. Note that by default all libraries are extracted to the target Jar. It became possible with addition of the new Extracted Directory element. Using such element you can extract a directory from a Jar file and place it

If you use GWT Compile Reports to analyze your GWT Application IntelliJ IDEA 10 will make this task easier. Using Tools | Generate GWT Compile Report action you can now generate a report and open it in the browser directly from IntelliJ IDEA: