Jetbrains Hybris

What is included in JetBrains Hybris?

Extension Import – Loads Hybris extensions with automatic dependency resolution.
ImpEx Editor – Formats, validates, and imports ImpEx to servers.
FlexibleSearch Console – Runs queries on remote Hybris instances directly.
Framework Setup – Configures Spring, Web, Ant, and Database tooling.
Core Capacity – Imports Eclipse, Maven, and Gradle Hybris extensions.
Important – Requires IntelliJ IDEA; not a standalone application.

What are the main benefits of JetBrains Hybris?

JetBrains Hybris Integration is a commercial IntelliJ IDEA plugin that adds SAP Commerce (Hybris) development support to the IDE. It turns generic Java tooling into a Hybris-aware workspace with dedicated editors and remote-instance actions.

Faster Onboarding – Imports a full Hybris project automatically.
Remote Execution – Runs ImpEx and FlexibleSearch against live instances.
Fewer Errors – Validates ImpEx and query syntax inline.
Code Navigation – Adds go-to-declaration and find-usages for Hybris files.
Build Coverage – Handles Eclipse, Maven, and Gradle extensions together.
Reliable Tests – Configures classpath for correct unit and integration tests.

What does JetBrains Hybris do?

JetBrains Hybris Integration adds SAP Commerce (Hybris) support to JetBrains IntelliJ IDEA. It imports an entire Hybris platform into the IDE and resolves extension dependencies and classpaths automatically, so projects compile and run unit and integration tests correctly. It also provides dedicated editors for ImpEx files and FlexibleSearch queries, both of which can be executed against a remote Hybris instance from inside the IDE. Without it, developers work with plain Java tooling that has no awareness of Hybris extension structure or ImpEx syntax.

What do you need to run JetBrains Hybris?

JetBrains Hybris Integration is an IDE plugin, not standalone software, so it runs only inside JetBrains IntelliJ IDEA or an IDE built on it. Its framework features depend on IntelliJ's Spring, Web, Ant, and Database connector tooling, so it is normally used with IntelliJ IDEA Ultimate rather than a bare editor. You install it through the IDE's plugin marketplace, and it is licensed separately from IntelliJ IDEA itself. In practice this means a working setup is the plugin plus an IntelliJ IDEA license, not the plugin alone.

How is JetBrains Hybris different from the free SAP Commerce Developers Toolset?

The core difference is the licensing and maintenance model: JetBrains Hybris Integration is a paid, closed-source plugin, while SAP Commerce Developers Toolset is a free, open-source fork maintained by EPAM and community contributors. Both descend from the same original Hybris Integration codebase and share capabilities such as extension import, ImpEx and FlexibleSearch editors, and remote-instance execution. The free toolset has been actively extended by the community, including support for SAP Commerce Cloud (CCv2) project structure. Before buying the paid plugin, it is worth checking whether the free toolset already covers your team's workflow.

Which Hybris workflows does the plugin support?

It targets the everyday tasks of SAP Commerce development: importing custom Eclipse, Maven, and Gradle extensions alongside the Hybris platform and keeping their classpath correct for compilation and testing. Its ImpEx editor adds automatic formatting, validation, find-usages, and go-to-declaration, and can push ImpEx scripts to a remote Hybris instance in one action. Its FlexibleSearch editor lets you write and run queries against a live instance without leaving the IDE. These remote actions remove the usual round-trip of switching to the Hybris Administration Console for routine ImpEx imports and query checks.

Who is JetBrains Hybris best suited for?

It is aimed at SAP Commerce (Hybris) developers and teams already standardized on IntelliJ IDEA who want Hybris-aware tooling instead of generic Java support. The concrete payoff is project setup: rather than manually wiring dozens of extension modules and their dependencies, the plugin imports the platform and resolves them automatically. For developers who frequently write ImpEx or FlexibleSearch, the in-IDE editors with validation and remote execution replace repetitive work in the Hybris Administration Console. It is less relevant for teams committed to Eclipse-based Hybris tooling, or those whose needs are met by the free open-source toolset.