News

VS Code Tool Supports Java 12, Adds Java Code Actions and Features

Visual Studio Code tooling has been updated with support for Java 12, new code actions, new debugging features, Maven enhancements and more.

Those goodies come with the Java Extension Pack, comprising a number of extensions ranging from Red Hat's language support to Java Test Runner to Visual Studio's AI-assisted IntelliCode among several others.

Available on the Visual Studio Code Marketplace, the extension pack has been installed nearly 1.7 million times.

In the April update to the tool, announced May 1, the dev team announced support for Java 12, which debuted in March.

"Java is now updating with a faster pace and we're following closely," said Xiaokai He in a blog post. "Thanks to the upstream update from JDT [Eclipse Java development tools], you can build your project with Java 12 features now with VS Code as well."

Other new features include: functionality to ease the getting-started process; performance improvements; new code actions to resolve ambiguous imports, generate toString() and more; a tweak to enable the debugger to show the logical structure of lists and maps, instead of the physical layout of the collections, along with several others; and Maven updates including customized commands, showing dependencies in a tree view and more.

Performance improvements include:

  • Improved editing performance when dealing with large amount of source file opened in the editor
  • Optimize start up and load time with better server initialization and lazy downloading Java source

"As we try our best improving performance, it would still take some time when importing a big Java project to Visual Studio Code," Xiaokai He said. "In this case, it would be helpful to show more progress details and let you know what's actually happening behind the scene. Instead of just showing the percentage of progress, we now added detailed step information into the status, such as inspecting location, configuring project, updating Maven dependencies, refreshing workspace and build workspace to let you know the wait is meaningful."

Microsoft's Java in Visual Studio Code site says the tooling for the ever-popular programming language:

  • Is fast and lightweight, free, and open-source
  • Supports multiple, or all the programming language developers use
  • Helps start a Java journey without installing and learning a complex IDE
  • Provides great microservices support including popular framework, container tooling and cloud integration
  • Improves productivity through smartness and collaboration features

The Java Extension Pack is still in preview and so far has received an average 4.1 rating (scale to 5) from 15 developers who reviewed it.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube