{"id":230932,"date":"2024-06-03T02:43:18","date_gmt":"2024-06-03T09:43:18","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/java\/?p=230932"},"modified":"2024-06-03T20:05:14","modified_gmt":"2024-06-04T03:05:14","slug":"java-on-visual-studio-code-update-may-2024","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/java-on-visual-studio-code-update-may-2024\/","title":{"rendered":"Java on Visual Studio Code Update – May 2024"},"content":{"rendered":"

Hi everyone, welcome to the May update for Visual Studio Code for Java! In this blog we are going to share an exciting new AI related feature for Java developers on Visual Studio Code. In addition, there will be several important Spring updates, so let’s get started.<\/p>\n

Rewriting your Java code with Copilot-based suggestions<\/strong><\/h3>\n

As our code undergoes updates and iterations, our business logic continues to grow in complexity. Meanwhile, Java versions are constantly evolving. Often, our older code can be replaced with newer, more efficient alternatives, not only improving their performance but also making the code more elegant, concise and secure. Previously, these tasks may have been done manually, but with the power of AI, many tasks can now be handled automatically.<\/p>\n

With the release of various AI products<\/a> at the Build conference 2024, we’re excited to announce an exciting update for Java developers on Visual Studio Code. In the Insider (Pre-release) version of our Extension Pack for Java, we’ve introduced a new feature: “Rewrite with new Java syntax<\/strong>” with Copilot! This feature integrates seamlessly with GitHub Copilot, so developers will need a GitHub Copilot license to access it.<\/p>\n

Here’s how the feature works, on your Java class, a new CodeLens text will appear above the name of the class: “Rewrite with new Java syntax<\/strong>“. Once the user clicks on this, it will trigger an inspection on the current Java class. Once the inspection is complete, Visual Studio Code will show several improvement suggestions and point users to the location.<\/p>\n

\"\"<\/a><\/p>\n

For each suggestion, additional CodeLens will appear and shows what the solution is (and what needs to be improved). The user can directly click on the CodeLens and this will bring up the GitHub Copilot inline chat dialog. The user can then see the code diff, and will be offered the choice of “Accept or “Discard”. If the user accepts the suggestion, then the workflow is over. Let’s see the first example where the for-loop can be refactored using IntStream.<\/p>\n

\"For<\/a><\/p>\n

Let’s look at another example, where our feature suggests that a multiple if and else-if logic can be directly re-written as a switch expression. By clicking on the CodeLens text, the code can be directly re-written as the improved code.<\/p>\n

\"Switch<\/a><\/p>\n

Inspecting part of the class<\/h5>\n

Sometimes, we may not want inspect the whole class because the code is too complex. The feature above also supports inspecting the part of the code. We just need select the code we want to inspect, and then click on the lightbulb on the left, select “Rewrite with Java syntax”. Here’s an example:<\/p>\n

\"Partial<\/a><\/p>\n

In this way, developers can inspect the code in a much more flexible way.<\/p>\n

This feature aims to leverage AI to offer helpful suggestions and seamless refactoring for Java developers for their code. We hope this can greatly boost developer’s productivity. If you have any feedback about this feature, please open an issue<\/a> on our GitHub repo!<\/p>\n

To use this feature, developer needs to install both Insider (Pre-release) version <\/span><\/span>Extension Pack for Java<\/span><\/span><\/a> and <\/span><\/span>GitHub Copilot<\/span><\/span><\/a> extensions. (with a GitHub Copilot license).<\/span><\/span><\/p>\n

Spring updates<\/strong><\/h3>\n

JPQL syntax highlighting<\/h4>\n

The Spring Boot Tools extension now features syntax highlighting for JPQL query strings. The syntax highlighting works for @Query annotations inside of Java source files as well as for named query property files. This makes reading those query strings much easier.\n(screenshot JPQL query syntax highlighting)<\/p>\n

\"JPQL<\/a><\/h4>\n

Add Starters directly from within `pom.xml` files<\/h4>\n

We added a clickable hint to pom.xml files of Spring Boot projects, directly\u00a0 in their dependency section. This clickable hint directly invokes the support to add additional Spring Boot starter modules. This improves discoverability and usability of this feature and makes it super easy to find and use.\n(screenshot add pom starters)<\/p>\n

\"Image<\/a><\/p>\n

Dashboard shows active profiles<\/h4>\n

The Spring Boot Dashboard now shows the active profiles of a running Spring Boot application directly side by side with the port the app runs on. This is available in the pre-release version.\n(screenshot active profiles in dashboard)<\/p>\n

\"Dashboard<\/a><\/h4>\n

Automatically convert application properties to YAML and back<\/h4>\n

The Spring Boot tools now offer actions to automatically convert `application.properties` files to YAML format and the other way around. This makes the switch to your (newly) preferred format super easy.\n(screenshot property conversion<\/p>\n

\"Convert<\/a><\/h3>\n

Performance and footprint improvements<\/h4>\n

The indexing infrastructure for Spring projects got improved. Previously, the mechanism was able to index about 6.5k Java source files inside of a single project before running out of memory. The latest versions can now index up to 60k Java source files instead within the same memory constraints. In addition to that the initial as well as ongoing performance of reconciling Java source files for Spring specific validations is now twice as fast as before.<\/p>\n

Testing Coverage<\/strong><\/h3>\n

In April, we released the Testing Coverage feature for our Test Runner extension in Stable version on Visual Studio Code. After release, we have received lots of positive feedback. However, we also received questions on how to use the feature. One popular question was around how coverage data can be reset for every execution.<\/p>\n

By default, the extension will append the coverage data (we use jacoco as the coverage tool, and\u00a0jacoco appends the coverage data by default<\/a>)<\/p>\n

If you want to reset the coverage data before every coverage execution, you can set the below setting:<\/p>\n

\"java.test.config\"<\/span>:<\/span> {<\/span>\r\n     \"coverage\"<\/span>:<\/span> {<\/span>\r\n         \"appendResult\"<\/span>:<\/span> false<\/span><\/span>\r\n     }<\/span>\r\n}<\/span><\/code><\/pre>\n
Install Extension Pack for Java<\/strong><\/h3>\n
To use all features mentioned above, please download and install Extension Pack for Java<\/a> on Visual Studio Code.<\/p>\n
\"Extension<\/a><\/p>\n
If you are a Spring developer working on a Spring Boot application, you can also download the Spring Boot Extension Pack<\/a> for specialized Spring experience.<\/p>\n
\"Spring<\/a><\/p>\n
Feedback and suggestions<\/span><\/strong><\/span><\/h3>\n
As always, your feedback and suggestions are very important to us and will help shape our product in future. There are several ways to give us feedback<\/p>\n