As we announced a short while ago, in the upcoming version 2019.2, IntelliJ IDEA and other IntelliJ-based IDEs are extending EditorConfig support, thus allowing you to manage all code style settings for each set of files individually. All you need to do is place an
.editorconfig file in the root directory containing the files whose code style you want to define. You can have as many
.editorconfig files within a project as needed, so you can specify different code styles for different modules. All options from the
.editorconfig file are applied to the directory where it resides as well as all of its sub-directories on top of the current project code style defined in Settings/Preferences | Editor | Code Style. If anything is not defined in
.editorconfig, it’s taken from the project settings.
In v2019.2, in addition to the standard EditorConfig options, we are adding a bunch of custom IntelliJ IDEA options, so now you can conveniently manage all you code style settings on the directory level.
Over the years, IntelliJ IDEA has accumulated support for a large array of technologies, and many of the technologies are no longer being actively maintained. We know that there are still people using these technologies, and up until now, we’ve been maintaining the plugins for them as part of the main IntelliJ IDEA source repository. However, our project has been growing, and carrying around this excess baggage is getting more and more difficult both for our users (as the plugins affect the size of the installation and potentially the performance of the IDE) and for our development team. At the same time, we’ve established procedures for maintaining a stable third-party plugin API, so we’re confident that moving the plugins out of the main repository will not affect their stability as the IDE evolves.
This is a guest blog post from Jordi Mon Companys, Product Manager at Códice Software
Context switching is one of the biggest hurdles developers need to overcome when in deep work mode. We also know that all of JetBrains IDEs – IntelliJ IDEA for one – are used across the world. In fact, IntelliJ IDEA is the world’s most used Java IDE. So, if these two things are correct, and we want Java programmers to benefit from versatile and powerful semantic version control, what should we do? Continue reading
This month’s annotated monthly is… not so annotated. The choice was either no annotated monthly at all, or a not-very-annotated monthly. I thought there was more value in option 2 than in option 1. However, it does lead to a new game: add witty annotations in the comments. Winner gets to do Java Annotated Monthly for the rest of their life.
Last Thursday we hosted a live webinar, presented by Brian Vermeer from Snyk. Brian talked about why application security is important, and what are some of the things developers can do to help improve the security of the applications they’re working on. Most importantly, he showed how we can use tools to simplify the process of identifying potential problems, including a plugin that lets us do it from inside IntelliJ IDEA.
The recording is now available, so even if you missed the live version you can still see it all here and now.