{"id":227355,"date":"2020-02-19T11:14:22","date_gmt":"2020-02-19T19:14:22","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/java\/?p=227355"},"modified":"2020-02-19T11:14:22","modified_gmt":"2020-02-19T19:14:22","slug":"java-on-visual-studio-code-update-february-2020","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/java-on-visual-studio-code-update-february-2020\/","title":{"rendered":"Java on Visual Studio Code Update – February 2020"},"content":{"rendered":"

Welcome back to the second update of Java on Visual Studio Code in 2020.<\/p>\n

In this update, we will show you the new ways to manage your dependencies and configure your multiple JDK. You will learn the additional tools you can leverage for popular frameworks and runtimes. There’re also a few new code actions and improvements to checkout. On to the update.<\/span><\/p>\n

Managing Dependencies<\/h3>\n

Whether your use any build tool or not, Java Dependency Viewer now provides you an easy way to deal with your dependencies.<\/p>\n

Maven<\/h4>\n

If you’re using Maven, now it’s very convenient for you to add dependency for your Maven project through Java dependency explorer by clicking the +<\/span>\u00a0 button as below.<\/p>\n

\"Image<\/p>\n

Other projects<\/h4>\n

If you’re not using any build tool like maven or gradle, and you want to reference binary jars in local file system, the experience is very similar to the maven experience above.<\/p>\n

\"Image<\/p>\n

Behind the scene, we’ve introduced a new setting java.project.referencedLibaries<\/span>. Below are the details about how to customize this setting.<\/p>\n

Include libraries<\/h5>\n

The libraries to reference is described using a set of glob patterns:<\/p>\n

\n
\"java.project.referencedLibraries\": [ \r\n    \"library\/**\/*.jar\", \r\n    \"\/home\/username\/lib\/foo.jar\" \r\n]<\/pre>\n<\/div>\n
In this way, all\u00a0.jar<\/code>\u00a0files in workspace’s\u00a0library<\/code>\u00a0folder, and\u00a0foo.jar<\/code>\u00a0in the specified absolute path is added to the project’s external dependencies.<\/p>\n
The referenced libraries is then watched by VS Code, and the project will be refreshed once there’s change in these dependent files.<\/p>\n
By default, VS Code will reference all jar files in workspace’s\u00a0lib<\/code>\u00a0directory using glob\u00a0lib\/**\/*.jar<\/code>.<\/p>\n
Exclude some libraries<\/h5>\n
If you want to exclude some libraries from the project, just expand\u00a0java.project.referencedLibraries<\/code>\u00a0to full\u00a0include-exclude-sources<\/code>\u00a0pattern and provide globs to\u00a0exclude<\/code>\u00a0field:<\/p>\n
\n
\"java.project.referencedLibraries\": { \r\n    \"include\": [ \r\n        \"library\/**\/*.jar\", \r\n        \"\/home\/username\/lib\/foo.jar\" \r\n    ], \r\n    \"exclude\": [ \r\n        \"library\/sources\/**\" \r\n    ] \r\n}<\/pre>\n<\/div>\n
In this way, any binary jar in\u00a0library\/sources<\/code>\u00a0folder is ignored from the project’s external dependencies.<\/p>\n
Attach source jars<\/h5>\n
By default, a referenced\u00a0{binary}.jar<\/code>\u00a0will try to search\u00a0{binary}-sources.jar<\/code>\u00a0under the same directory, and attach it as source if one match is found.<\/p>\n
If you want to manually specify a jar as source attachment, you can provide a key-value map in the\u00a0sources<\/code>\u00a0field:<\/p>\n
\n
\"java.project.referencedLibraries\": { \r\n    \"include\": [ \r\n        \"library\/**\/*.jar\", \r\n        \"\/home\/username\/lib\/foo.jar\" \r\n    ], \r\n    \"exclude\": [ \r\n        \"library\/sources\/**\" \r\n    ], \r\n    \"sources\": { \r\n        \"library\/bar.jar\": \"library\/sources\/bar-src.jar\" \r\n    } \r\n}<\/pre>\n<\/div>\n
In this way,\u00a0bar-src.jar<\/code>\u00a0is attached to\u00a0bar.jar<\/code>\u00a0as its source.<\/p>\n
Once external jar files are added, you can also see their file paths as description in Java Dependency Explorer.<\/p>\n
\"Image<\/p>\n
\"Image<\/p>\n
\"Image<\/p>\n
<\/h3>\n
Configure local JDK runtime<\/h3>\n
As Java evolves, lots of Java developers need to deal with multiple Java runtimes. Now we support a new preference mapping java.configuration.runtimes<\/code> for Java execution environments. VS Code will detect the runtime required for your project and choose the appropriate one configured. See below as an example.<\/p>\n
\"java.configuration.runtimes\": [\r\n        {\r\n            \"name\": \"JavaSE-1.8\",\r\n            \"path\": \"\/usr\/local\/jdk1.8.0_201\"\r\n        },\r\n        {\r\n            \"name\": \"JavaSE-11\",\r\n            \"path\": \"\/usr\/local\/jdk-11.0.3\",\r\n            \"sources\" : \"\/usr\/local\/jdk-11.0.3\/lib\/src.zip\",\r\n            \"javadoc\" : \"https:\/\/docs.oracle.com\/en\/java\/javase\/11\/docs\/api\",\r\n            \"default\":  true\r\n        },\r\n        {\r\n            \"name\": \"JavaSE-12\",\r\n            \"path\": \"\/usr\/local\/jdk-12.0.2\"\r\n        },\r\n        {\r\n            \"name\": \"JavaSE-13\",\r\n            \"path\": \"\/usr\/local\/jdk-13\"\r\n        }\r\n    ]\r\n<\/code><\/pre>\n
Runtime name must be one of: “J2SE-1.5”, “JavaSE-1.6”, “JavaSE-1.7”, “JavaSE-1.8”, “JavaSE-9”, “JavaSE-10”, “JavaSE-11”, “JavaSE-12”, “JavaSE-13”. We will update the list with each supported release of the JDK<\/p>\n
Extensions for popular Java Frameworks and Runtimes<\/h3>\n
If you’re working with popular Java Frameworks such as Spring Boot and MicroProfile, Visual Studio Code has you covered as well. Below are some exciting new capabilities now available with those extensions<\/p>\n
    \n
  1. Spring Boot Tools<\/a> now reports connection failures in live hover.<\/li>\n
  2. Newly released MicroProfile Extension Pack<\/a> now includes MicroProfile Starter<\/a> for you to quickly generate a MicroProfile Maven project along with development tools for runtimes such as Open Liberty<\/a> and Quarkus<\/a> with lots of new features.<\/li>\n
  3. If you’re working with any Red Hat server and runtime products such as Wildfly or JBoss, checkout Server Connector<\/a> which allows you to start, stop and deploy to any of them.<\/li>\n<\/ol>\n
    More enhancements<\/h3>\n
    The latest updates also brings a lot of other enhancements for Java experience in Visual Studio Code.<\/p>\n
      \n
    1. New code actions\n
        \n
      • Remove the\u00a0final<\/code>\u00a0modifier.<\/li>\n
      • Assign statement to new variable\/field.<\/li>\n
      • Remove redundant interfaces.<\/li>\n
      • Add missing case labels in switch statements.<\/li>\n<\/ul>\n<\/li>\n
      • Added java.import.gradle.offline.enabled<\/code>\u00a0preference.<\/li>\n
      • Expose full completion proposals to 3rd party extensions. This will enable other extensions such as IntelliCode to provide you better IntelliSense experience without impacting the completion performance.<\/li>\n
      • Java Dependency Viewer\n
          \n
        • add Collapse All<\/span>\u00a0 support<\/li>\n
        • Support right click context menu for view nodes<\/li>\n<\/ul>\n<\/li>\n
        • Maven\n
            \n
          • Support to debug favorite commands.<\/li>\n
          • Add shortcut to view output when error occurs.<\/li>\n
          • Support to browse for local Maven binary if not found.<\/li>\n<\/ul>\n<\/li>\n
          • \u00a0Debugger\n
              \n
            • Provide context menu to continue\/pause all\/other threads.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\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