We are excited to announce that the upcoming IntelliJ IDEA 2018.3 will come with initial support for GitHub pull requests, along with a couple of other features worth talking about in detail.
GitHub Pull requests
Now you can view all pull requests from your GitHub repository as a list inside the IDE. They are available in the brand new GitHub Pull Requests tool window. Select Main menu | VCS | Git | View Pull Requests and view the state of a PR, current label, and assignee, if any. In the right pane, you can view the altered files and use the diff to preview the changes.
We plan to add actions such as merge, close, comment, and more in the forthcoming releases. For now, you can create a local branch from a PR via the context menu and then merge it as a regular branch. From the same context menu, you can quickly open a pull request on github.com.
The new IntelliJ IDEA 2018.2.5 bug-fix update is ready for you to download. This minor update includes a series of bug fixes and improvements: Continue reading
In this latest post about Kotlin support in Spring plugins in IntelliJ IDEA, we’d like to point out that Spring Boot is also fully supported for Kotlin. When you run a Kotlin main function that starts a Spring Boot application, it will be automatically recognized as a Spring Boot Run configuration:
Not so long ago, IntelliJ IDEA 2018.1 Ultimate Edition introduced some initial support for Kubernetes through the brand new Kubernetes plugin. The forthcoming IntelliJ IDEA 2018.3 takes it even further and now the Kubernetes plugin gets Helm support!
In the blog post covering the first EAP build of IntelliJ IDEA 2018.3, we only briefly mentioned the availability of Helm support in the Kubernetes plugin. Now the time has come to dive into the details.
Please bear in mind that you need to install not only the Kubernetes plugin v2018.3, but also the Go template plugin. After this is done, the IDE will correctly resolve the Helm resource template files and provide you with our well-known editing support: code completion, rename refactoring, and, of course, inspections and quick-fixes.
We are very much committed to improving accessibility across our products and I’m happy to announce that with the upcoming release of IntelliJ IDEA 2018.3 we’ve made some notable improvements.
High Contrast Theme
We’ve added support for a new High Contrast Theme, which can be accessed using the drop-down list from the theme options under Preferences (Settings) | Appearance & Behaviour or via the Ctrl-` shortcut on macOS, Windows, and Linux.
The main news so far has been the release of Java 11. It’s not a large release in terms of new developer functionality since Java 10, but it is the first Long Term Support Release since Java 8, so if you’ve been hanging around on Java 8, now’s the time to look at all new things that made it into Java 9, 10 and 11. Java 11 also removes things. This, like, never happens in Java. Also noteworthy, Oracle changed its licensing and support model since Java 8. Read this month’s Annotated Monthly to find out more.
Here is the new blog post on Kotlin and Spring support in IntelliJ IDEA.
The Spring Framework supports reading values from different kinds of sources using the
@Value annotation. Completion, reference navigation, and folding property names with their values is now supported for Kotlin in IntelliJ IDEA: Continue reading
Another IntelliJ IDEA 2018.3 EAP with more new goodies is now available for download! Let’s review what is inside the fresh EAP build!
For a start, the upcoming IntelliJ IDEA 2018.3 updates Git multi-repository projects significantly faster than before. Previously, the IDE could only fetch repositories one by one. Now, the IDE fetches all git repositories in the project in parallel during the project update.
Posted in EAP Releases
It’s time for the next topic in the series of blogs on using Spring Framework with Kotlin support in IntelliJ IDEA.
Kotlin classes are final by default, but some Spring functionality requires classes to be open. For instance,
@Configuration classes should be extendable, and methods annotated with
@Async must also be extendable. If you don’t want to bother with it, there is the all-open plugin as well as the spring plugin for Kotlin compiler. But if you don’t like the idea of modifying Kotlin rules by compiler plugins and don’t mind an additional
open modifier on your classes and methods, then IntelliJ IDEA offers an inspection that checks that all necessary classes and members are declared open:
If you stay up to date on news from the Java community, you may have heard that Oracle have changed their support model for Java. Some news is even suggesting that we now have to pay to use Java – this is not true!