JetBrains has partnered with Mend.io, a trusted name in application security. This collaboration will help us continue providing the tools you need to develop secure applications with ease and confidence in our IDEs and Qodana. For the best user experience, make sure to use the latest stable version 2024.3.2. Why Mend? Trusted by industry giants […]

JetBrains has partnered with Mend.io, a trusted name in application security. This collaboration will help us continue providing the tools you need to develop secure applications with ease and confidence in our IDEs and Qodana. For the best user experience, make sure to use the latest stable version 2024.3.2.

Why Mend?

Trusted by industry giants like Google and Comcast, Mend.io offers a reliable application security platform. It helps organizations build mature AppSec programs, shifting from reactive vulnerability management to proactive risk mitigation. With Mend’s expertise, our users gain access to a robust solution that simplifies security and boosts code quality.

What’s new?

Our Package Checker plugin has long been a reliable tool for identifying vulnerabilities in third-party dependencies and suggesting safe updates. By switching to Mend.io as our software composition analysis (SCA) provider, we’re ensuring that these capabilities remain effective and up to date.

Malicious package detection

Thanks to this partnership, you can now identify malicious packages – those specifically designed to harm systems. Mend strongly advises removing such packages immediately to protect your code and systems.

Powered by Mend.io, the Malicious Dependency inspection helps you:

• Detect harmful npm and PyPI packages.

• Prevent commits with malicious dependencies, protecting your repositories.

Malicious package detection is also available in Qodana.

Vulnerability detection

The popular Vulnerable Path functionality, which helps pinpoint the exact source of a vulnerability, will return with the upcoming 2025.1 version of JetBrains IDEs, giving you added precision when managing your code dependencies.

Basic functionality remains

The bundled Package Checker plugin will continue to provide a reliable way to keep your code secure with the help of the following basic features:

• Dependency scanning. Helps identify vulnerabilities and threats in third-party dependencies.
• Safe updates. Suggests secure versions of dependencies, allowing you to fix vulnerabilities easily.
• Smooth IDE integration. Highlights issues directly in the editor and provides details in the Problems | Vulnerable Dependencies tab or via Analyze | Vulnerable Dependencies.

Looking ahead

This update brings incremental, yet valuable, improvements to the security features in JetBrains IDEs and Qodana. We’re committed to enhancing these capabilities further and providing you with the tools needed to build secure applications.

Be sure to update your tools and try the new features once they are available!

Go to Source

In this release, you’ll find improvements to the UI, reworked internals for various components, and a binary-enabled textgen. MPS 2024.3 also brings enhanced support for icons, an applicability condition for quick-fixes, and numerous platform updates. DOWNLOAD MPS 2024.3 What’s new Let’s check out the new features we’ve prepared for you in this release. Top-level folder […]

In this release, you’ll find improvements to the UI, reworked internals for various components, and a binary-enabled textgen. MPS 2024.3 also brings enhanced support for icons, an applicability condition for quick-fixes, and numerous platform updates.

DOWNLOAD MPS 2024.3

What’s new

Let’s check out the new features we’ve prepared for you in this release.

Top-level folder for transient and checkpoint models

The ProjectView tool now provides three top-level folders to keep the structure of the project better organized:

• Project Name
• Modules Pool
• Checkpoints and Transient Models

The Checkpoints and Transient Models folder is always displayed below the Modules Pool, and is empty unless any transient or checkpoint models are available. These models are displayed under this folder, and not at the top level as they used to be.
As a side effect, the new Checkpoints and Transient Models folder allows the ProjectView to remember the expanded and collapsed subtrees of the project structure across MPS restarts.

Enable preview tag option

The following options to enable/disable the Preview Tab provided by the IntelliJ Platform are now respected by MPS and guarantee the same behavior of the editor as in other JetBrains tools:

• Settings | Editor | General | Editor Tabs | Opening Policy | Enable preview tab
• Logical View | Behavior | Enable Preview Tab

Applicability condition for a quick-fix

A new section named applicable has been added to Quick-Fix definitions to let you control the applicability of a quick-fix. The default value <always> guarantees unrestricted applicability.

Icon handling

Icons and images that use a path relative to the module are no longer copied during generation next to the places of their individual usage. Instead, they are copied to the distribution module once as image files and are available for use at this single location. This has two immediate benefits: avoiding the duplication of image files to save disk space and the ability to access the images both from the distribution and from the source module.

Constant icons

In addition to the existing TextIcon and FileIcon concepts, a new ConstantFieldIcon concept is now available. It allows an icon to be specified by reference to a concrete static field declaration holding an instance of javax.swing.Icon.

TextGen binary outcome

Inspired by the need for better handling of icon files, we’ve added a new mechanism to produce binary output during the TextGen process, instead of text. The new API consists of a write operation that directly manipulates data as instances of byte[].

Tool windows migrated away from ProjectComponent

All tool windows, such as Inspector, HierarchyView, and Usages, have been reworked to no longer follow the long-deprecated mechanism of the IntelliJ Platform’s project components (ProjectComponent). The changes to the API have been minimal, but for some tool windows, there is a change in how they are obtained from code:

• The Project.getComponent() method no longer returns any of the tool windows.
• Tools that are implemented as an MPS tool concept can be obtained using com.intellij.openapi.project.Project.tool<ToolConcept>.
• Tools that are frequently used from Java provide a static getInstance() method:
  
  • UsagesViewTool.getInstance()
  • InspectorTool.getInstance()

  
  

• The Inspector tool is traditionally also available from EditorContext.inspectorTool().

IntelliJ Platform components and services

In addition to tool windows, most of the MPS core functionality has been reworked not to use IntelliJ IDEA’s ApplicationComponent and ProjectComponent.

MPS used to rely heavily on the IntelliJ Platform facilities to compose the complete application. Now, most of the legacy components have been refactored to use contemporary MPS or IntelliJ IDEA APIs (like IntelliJ IDEA’s application/project services and extension points, MPS’ CoreComponents and extensions, etc.). There are still a few components left, which the MPS team plans to get rid of completely in the next release.

Most users probably won’t notice any difference, with the exception of reduced startup times.

Please consult the Migration Guide if your code fails to locate any of the platform components because it uses an obsolete retrieval mechanism.

Switched to the new UI

MPS now uses the new UI. The old version of the UI can be enabled by installing the Classic UI plugin.

More new features…

Check out the What’s New page to learn all about the new features.

You can find a full list of fixed issues here.
Your JetBrains MPS team

Go to Source