What an exciting month May was! The Java Community Process was flung into the spotlight as the Executive Committee voted against Jigsaw, raising questions like: how does this impact Java 9? What happens next? And what is the JCP anyway? Add to this the announcement of some exciting Android-related news, and we have a very full Java Annotated Monthly!
In this week’s Git video, Gary and I look at how you can Annotate your code to see who made which changes. We also show how you can use this information to understand a bit more about the context of a particular change.
Earlier we mentioned that IntelliJ IDEA 2017.2 EAP features improved control flow analysis that infers the contracts of certain methods of String, Array, Collection and Map classes.
With today’s EAP build, this analysis becomes even smarter. If that sounds like something you might be interested in, read on and see how the new checks are going to work.
Last week we’ve published a new IntelliJ IDEA 2017.2 EAP build, which, among various bugfixes and improvements, brings a new experimental feature, we think you may find very interesting. Because it’s still work in progress, you need to explicitly enable it via VM property -Dide.run.dashboard=true, or through the Registry.
After that, you will find that the traditional Run tool window for Spring Boot applications was replaced with the new Run Dashboard (in the future we plan that replacement for other app types, too.)
This new dashboard lets you explore and manage multiple Run configurations at once, with the list of Run configurations and their status on the left, and details and application-specific information on the right. Also, you get the tool bar that is handy to issue commands like run, stop, or restart.
For example, Spring Boot applications display the recently introduced Endpoints tab:
If you prefer so, the new tool window can look exactly like the Run tool window. Just click the Show Configurations button on the left toolbar, and then use the tabs on top to switch between running applications:
We’re very excited about this new feature and believe that it can be applied not only to Spring Boot, but to many other types of applications (and maybe not only applications). This is why we’d like to ask you for your feedback. Please give this new feature a try and share with us both your impressions and improvement suggestions. We hope your feedback will help us better understand the possible usage scenarios and put them in IntelliJ IDEA 2017.2.
After a few, blissful, drama-free issues, this month we look into the tension between the community and the Stewards of Java (again), this time the topic is Modularity. Feedback from the community is always a Good Thing to help improve the platform, but when Jigsaw was due for release with Java 9 in two months it gets a little more… interesting. Java 9 isn’t the only news, as usual we’re covering Java’s future, linking to blogs and tutorials for Java (including Android) code and design, and we’ve added a whole new section for Java Performance this month.
It’s been only a month and a half since the release of IntelliJ IDEA 2017.1, but it’s time to shed a light on the next major update on which we’re going to work the entire Summer.
This week we’ve published IntelliJ IDEA 2017.1.2, an update to its current stable release version, and now it’s time to move forward—so say hello to IntelliJ IDEA 2017.1.3 EAP.
In it you will find Kotlin plugin 1.1.2 along with updates to the built-in JRE, among which is better font rendering on Fedora core 25 (Wayland), and an up-to-date macOS binaries signature certificate.
Develop with Pleasure!
The just-out IntelliJ IDEA 2017.1.2 update brings important bugfixes and overall improvements.
Among notable changes:
- JUnit 5 M4 support (incl. running parametrized tests)
- Support for the new Typescript 2.3 language features (e.g. for await)
- An important fix for the freeze while editing Gradle build files
For the complete list of changes, see the release notes.
Get it via Help | Check for Updates | Download and install, or let the Toolbox App do it for you!
UPDATE: If you download Windows “.zip” bundle, Kaspersky and some other antiviruses may flag “jre32\bin\unpack200.exe” as a virus. We’re investigating this issue. The workaround is to use “.exe” bundle and not to choose 32-bit JRE.
Develop with Pleasure!
- Better font rendering on Linux
- Find in Path usability improvements
- Various Gradle support errors
Major new features:
- Manual columns reordering in Git Log
- Better completion for package.json fields
- Support for function-based indices in Oracle and Postgres
For the complete list of changes, refer to the release notes.
Develop with Pleasure!