Jmix 2.8 released

Announcements
#1

We are pleased to announce the release of version 2.8 of the Jmix framework and Studio! The framework is available in our artifact repositories, and you can update the Jmix Studio plugin in your IntelliJ IDEA.

To learn about the new and notable features of this release, please check our blog post.

The what’s new section of the documentation includes guidance on upgrading, along with a full list of new features and changes that may cause incompatibility with earlier versions.

The documentation now shows information about version 2.8 by default. You can switch to previous versions using the selection controls at the bottom left corner or in the page header.

We’re looking forward to your feedback!

5 Likes
#2
#3

Hi everyone! Please write your questions to the Jmix team below. We’ll cover the topics during the release webinar.

#4

A lot of good stuff, congratulations!

I like the side panel layout a lot. Can we get that also as a create new view template in the studio?
As an alternative to the classic Detail views, where a complex Detail is not needed.
I can see how not having detail view of the class and its XML descriptor would reduce the size of the source code, thus making things simpler for the dynamic system, and saving tokens if using AI.

Kind regards,
Mladen

Kind regards,
Mladen

2 Likes
#5

Dear Support

Our production machine is running with Debian 13, JRE 21, MariaDB, Jmix 2.8 WAR

https://docs.jmix.io/jmix/whats-new/index.html#mariadb-uuid

Do I understand correctly, that I have to run

./gradlew bootRun --args='--main.liquibase.clear-checksums=true'

on the production machine ??

  • I would have to install gradle ( where the Debian Version of Gradle is too old for Java 21 )
  • I would have to install a jdk
  • copy the gradlew, build.gradle and gradle.properties to the production machine
  • I would need to install the full source on the production machine ??

Actually I did start the application and update the database with the new checksum

UPDATE DATABASECHANGELOG SET MD5SUM = '9:497e2cd4292d8132503eae3d11826878' WHERE MD5SUM = '9:cbb1a286a79646aca73adc1582204021'

Regards

Felix

#6

Hello Felix!

Thank you for pointing out the gap in the description — I’ve created the issue to expand the documentation.

Running the application with ./gradlew bootRun and this argument is the simplest option, especially if the number of affected checksums is large.

Your approach works perfectly well too.

Alternative approaches may be found also in issue instruction:

  1. Set the same property in application.properties and build a separate version of the application for a one-time run.
  2. Manually specify the checksums in <validCheckSum> for each affected changeSet.

Regards,
Dmitry