{"id":225753,"date":"2019-06-24T10:00:17","date_gmt":"2019-06-24T17:00:17","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=225753"},"modified":"2019-11-14T15:05:53","modified_gmt":"2019-11-14T23:05:53","slug":"java-on-visual-studio-code-june-update","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/java-on-visual-studio-code-june-update\/","title":{"rendered":"Java on Visual Studio Code June Update"},"content":{"rendered":"

Welcome to the June update of Java on Visual Studio Code!<\/p>\n

Earlier this month, we shared our new Java Installer for Visual Studio Code<\/a>, which aims to help new Java developers to get their environment ready and start coding in just a few clicks. In this update, we\u2019d like to share a couple new features and enhancements delivered during last few weeks.<\/p>\n

More code actions<\/h3>\n

Developers need refactoring and code actions to achieve high productivity, so we’re bringing more of those features to you.<\/p>\n

Enhanced \u201cGenerate getters and setters\u201d<\/h5>\n

In addition to bulk generate getters and setters for all member variables, if the class has more than one field, the source action will also prompt a quick pick box which allows you to select the target fields to generate the accessor methods.<\/p>\n

\"\"<\/p>\n

The source action is also aware of the java.codeGeneration.generateComments<\/em> preference and will use it to decide whether to generate comments for getter and setter methods.<\/p>\n

Generate Delegate Methods<\/h5>\n

This new code action enables generating delegate methods.<\/p>\n

\"\"<\/p>\n

Generate Constructor<\/h5>\n

This source action helps adding constructor from super class.<\/p>\n

\"\"<\/p>\n

Assign parameter to new field<\/h5>\n

This source action assigns parameter to new field for unused constructor parameter(s).<\/p>\n

\"\"<\/h4>\n

Performance improvements<\/h3>\n

A set of changes have been made to further improve performance of Java in Visual Studio Code, including a fix for I\/O issue on Windows platform, reducing memory footprint for large projects with deep modules and batch project imports. VS Code is a lightweight editor and we’d like to make sure it still feels just like an editor when despite more and more features being added to it.<\/p>\n

Debugger updates<\/h3>\n

Debugging is the most frequent used feature second only to code editing. We’d like you to enjoy debugging Java in Visual Studio Code.<\/p>\n

Show more meaningful value in variable window and hover tool-tip<\/h5>\n

We’re now providing additional detailed information for variables during debug<\/p>\n

    \n
  • For the classes that override ‘toString<\/em>‘ method, show toString()<\/em> details.<\/li>\n
  • For Collection and Map classes, show an additional size=x details.<\/li>\n
  • For Entry, show key:value details<\/li>\n<\/ul>\n

    \"\"<\/p>\n

    New HCR button<\/h5>\n

    To better expose the hot code replace feature and let you control it more explicitly, we’ve added a new button to the toolbar and provided a new debug setting `java.debug.settings.hotCodeReplace` to allow you control how to trigger HCR. Default to `manual`.<\/p>\n

      \n
    • manual – Click the toolbar to apply the change to running app<\/li>\n<\/ul>\n

      \"\"<\/p>\n

        \n
      • auto – Automatically apply the changes after compilation. This is the old behavior.<\/li>\n
      • never – Never apply the changes<\/li>\n<\/ul>\n

        See HCR in action<\/p>\n

        \"\"<\/p>\n

        Global setting for selecting debug console<\/h5>\n

        While VS Code offers a powerful Debug Console\u00a0with REPL (Read-Eval-Print Loop)\u00a0functionality, one major restriction of it is it doesn\u2019t accept input. For those programs which need to take console input, developers need to specify to use integratedTerminal instead of internalConsole in launch.json.<\/p>\n

        \"console\": \"integratedTerminal\"<\/pre>\n
        However, this is not convenient if you need to do it repeatedly. Now we\u2019re introducing a global setting, java.debug.settings.console<\/em>. you can use this setting to configure the default debug console so you don\u2019t need to change the launch.json every time.<\/p>\n
        \"java.debug.settings.console\": \"integratedTerminal\"<\/pre>\n
        Other updates<\/h3>\n
        Maven<\/h5>\n
        2 new configs are now available for Maven extension<\/p>\n
          \n
        1. pomfile.globPattern<\/em> \u2013 specified how the extension search for POM file.<\/li>\n
        2. pomfile.autoUpdateEffectivePOM<\/em> \u2013 specifies whether to update Effective-POM automatically.<\/li>\n<\/ol>\n
          Test Runner<\/h5>\n
          In recent releases, we\u2019ve added support for a couple additional JUnit5 annotations, such as @Nested<\/em> and @TestFactory<\/em>. Test runner will also automatically show the test report after execution now.<\/p>\n
          Sign up<\/h3>\n
          If you’d like to follow the latest of Java on VS Code, please provide your email with us using the form below. We will send out updates and tips every couple weeks and invite you to test our unreleased feature and provide feedback early on.<\/p>\n
          <\/div>\n