- XRebel 2020.3.1September 2020
- XRebel 2020.2.0June 2020
- XRebel 2020.1.1February 2020
- XRebel 2020.1.0November 2019
What's New in XRebel 2020.3.1
XRebel 2020.3.1 introduces a number of new features and integrations, including an onboarding tour that makes it easier for new and experienced users to explore the latest XRebel features.
You can download XRebel 2020.3.1, or view the changelog, by selecting an option below.
New Features and Support in XRebel 2020.3.1
One of the more exciting features in XRebel 2020.3.1 is the new XRebel tour. It walks through all the features XRebel has to offer in a demo environment.
Additionally, XRebel 2020.3.1 adds support for Reactor Netty in Spring Boot 2. This support makes Spring Boot 2 a fully supported framework with XRebel.
Bug Fixes and Usability Improvements
XRebel introduces a handful of bug fixes, and a few nice usability improvements that make the XRebel experience better. These include a Javaassist exception in Hibernate, and UI issues that relate to horizontal scroll while using XRebel.
For a full list of features, fixes, and improvements, please visit the XRebel changelog.
What’s New in XRebel 2020.2.0
XRebel 2020.2.0 is now available! This release introduces numerous bug fixes, features, and improvements that make XRebel more effective for developers. Please download the latest version, or view the full changelog by clicking the buttons below.
New Features in XRebel 2020.2.0
XRebel 2020.2.2 marks major improvements in both user experience and functionality. With a number of features that allow developers to do more with the plugin, added support for hibernate, and the new Eclipse plugin integration with JRebel, there are plenty of new features to love.
JRebel and XRebel Combined Eclipse Plugin
The JRebel plugin for the Eclipse IDE now features a native XRebel integration. Enjoy all the benefits of XRebel while using JRebel in Eclipse, and toggle use of JRebel and XRebel at will.
In this latest release, XRebel also adds support for several new technology versions, including Java 13, Java 14, and Hibernate 5.0.
Java 13 and Java 14
XRebel now works with Java 13 and Java 14, allowing developers to trace the performance impact of new language features.
XRebel 2020.2.0 adds support for Hibernate 5.0, making it much easier for developers to trace and assess database queries in Hibernate ORM.
Improvements to Sharing View
XRebel 2020.2.0 introduces several new sharing features and improvements, giving users the ability to:
- Notate sessions captured in sharing view.
- Compare saved traced in sharing view.
- Preserve tree state in sharing view.
Other Improvements and Bux Fixes
This latest version also introduces improvements to UX and performance, with improved comparison in CPU view and faster Diff load time. Bug fixes included in the update target a handful of UI issues and user-reported bugs.
What's New in XRebel 2020.1.1
XRebel 2020.1.1 is now available for download! This release is user-focused, with two new features designed to make life easier for XRebel users. You can download XRebel 2020.1.1 by clicking the button below.
XRebel 2020.1.1 New Features
This latest version introduces two new features; a moveable toolbar, which lets users place the XRebel toolbar where desired, and simplified remote licensing, which makes XRebel configuration for microservices, containers, and remote servers a much easier — and faster — process for developers.
Moveable XRebel Toolbar
The XRebel toolbar is now moveable! This UX feature fixes a common complaint from developers and offers increased ease-of-use for XRebel users. If XRebel is blocking your view of critical browser information, simply click the top right corner of the XRebel banner and position it in a more convenient location.
Absolute Time on Trace View
XRebel now supports viewing more in-depth details in your trace view. This means that XRebel users will now be able to get the exact amount of time it takes for a method to be processed. With XRebel 2020.1.1, you will be able to immediately see this in the trace view whenever you make a request.
Simplified Remote Licensing
XRebel 2020.1.1 introduces the ability to configure your licenses through JVM arguments – which means users can now configure XRebel on remote servers, microservices, and containers faster than ever.
XRebel 2020.1.1 Changelog
Looking for the full XRebel 2020.1.1. changelog? You can view the current XRebel version changelog by clicking the link.
In Case You Missed It
XRebel 2020.1.0 introduced dedicated support JDK's CompletableFuture API, including two new ways to trace parallelized threads — the Trace Tree View and Gantt Chart View.
You can read more about these new XRebel 2020.1.0 features by clicking the release link on the sidebar.
What’s New in XRebel 2020.1.0
With XRebel 2020.1.0, we're introducing dedicated support for JDK's CompletableFuture API! This is a big step toward making XRebel the go-to tracing tool for reactive programming in Java.
Trace Tree View
This feature plugs smoothly into the existing XRebel trace tree: CompletableFuture tasks are indicated by the icon.
CompletableFuture support takes advantage of the reactive programming support XRebel already has. Any work that is parallelized into a separate thread is indicated by the fork point icon . This will help you understand how your CompletableFuture tasks actually map to threads.
Gantt Chart View
We are especially proud of the new Gantt chart view, which helps you drill down into CompletableFuture tasks and their interdependencies.
The Gantt chart view displays all CompletableFuture tasks from the current request as a timeline — with the X-axis representing time since the beginning of the current request. Each task is then represented as a bar, making it easy to determine the timing and duration of a given task.
The connectors help to visualize inter-task dependencies. For example, some tasks depend on the completion of a number of other tasks (e.g. thenCombine), but other tasks might require completion of just one of their parents (e.g. acceptEither). The Gantt chart view visualizes this distinction, making it easy to trace the "critical path" (i.e. which asynchronous calls affected the overall request time) through the graph of asynchronous operations.