Jmix 2.4 release candidate

Hi everyone,

We are happy to announce that the release candidate of Jmix v.2.4 is published in our artifact repositories! To try out the RC, please restart your IDE and select “Show unstable versions” when creating or updating a project.

Jmix Studio 2.4 can be downloaded from the nightly channel.

For more information on the new features, improvements, and upgrade instructions, please refer to the release notes. The documentation for this release is currently incomplete, but we are actively working on it.

We would greatly appreciate your feedback on the RC. If you encounter any issues, please let us know.

The final release 2.4 is expected by the end of October.

7 Likes

Dear Mr Konstantin Krivopustov,
Congratulation Jmix team! Thank you for your hard and effective working.
We are waiting for long time of this version.
Most of functions we want to see is: “Support for external BPM engine” at Jmix Roadmap · GitHub.
This function will included in 2.4 release?

Dear Nguyen Tien Ha,

We are still working on this feature, and unfortunately it won’t be included in the October release.

Regards,
Konstantin

1 Like

Hi Nguyen Tien Ha,

Glad to here from you! The feature you’ve mentioned is in progress, but won’t be presented as a part of Jmix 2.4. We decided to deliver this option as a separate offer named “Open BPM”. While integrating remote BPM engine to Jmix, we found that it makes the exisiting development process too complex. Bringing this option as a dedicated solution enables addressing wider use-cases in process automation area and better leverages Jmix capabilities as a BPM backend. You can find more details about the actual product vision following the link and book a demo. Our team will be happy to demonstrate you the working concept and recieve feedback.

2 Likes

I just wanted to try this RC release but when I tried to install the nightly build of the studio, I still saw the old one that was built in Sep 2024:

image

Hi

Latest Jmix Studio nightly builds require IDEA 2024.2, so you need to update IDE to get this versions.

Thanks.
Now I tried to migrate, got the following error:

image

Hi,

Thank you for report.
I have created an issue, we already working on it.

Regards,
Mikhail

1 Like

Hi @m.fedoseev
Note that, I’m trying it for a composite project.

1 Like

Since I saw the platform 2.4 has been released and the above issue is resolved in build 242, I gave a try and now getting the following error, seems like from grid-export addon:

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/mak/Projects/inteaccHCM copy 2/inteaccld/build.gradle' line: 12

* What went wrong:
A problem occurred evaluating project ':inteaccld'.
> Could not find method implementation() for arguments [io.jmix.gridexport:jmix-gridexport-flowui-starter] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

* Try:
> Run with --stacktrace option to get the stack trace.

Here is the gradle file of the addon project within the composite project:

configurations.implementation {
    exclude group: 'com.vaadin', module: 'hilla'
    exclude group: 'com.vaadin', module: 'hilla-dev'
}

buildscript {
    repositories {
        gradlePluginPortal()
    }
    dependencies {
        classpath 'io.jmix.gradle:jmix-gradle-plugin:2.4.0'
        implementation 'io.jmix.gridexport:jmix-gridexport-flowui-starter'
    }
}

group = 'com.company'
version = '0.0.1-SNAPSHOT'

subprojects {
    apply plugin: 'java-library'
    apply plugin: 'maven-publish'
    apply plugin: 'io.jmix'

    repositories {
        mavenCentral()
        maven {
            url = 'https://nexus.jmix.io/repository/public'
        }
        maven {
            url 'https://maven.vaadin.com/vaadin-addons'
        }
    }

    jmix {
        bomVersion = '2.4.0'
        projectId = 'ld'
    }

    group = this.group
    version = this.version

    def props = new Properties()
    buildFile.withInputStream { props.load(it) }
    def subArchivesBaseName = props.getProperty('archivesBaseName')
    def archName = subArchivesBaseName.substring(1, subArchivesBaseName.length() - 1)

    java {
        withSourcesJar()
    }

    artifacts {
        archives sourcesJar
    }

    publishing {
        repositories {
            maven {
                url = 'https://myrepo/releases/'
                credentials {
                    username rootProject.hasProperty('uploadUser') ? rootProject['uploadUser'] : 'admin'
                    password rootProject.hasProperty('uploadPassword') ? rootProject['uploadPassword'] : 'admin'
                }
                allowInsecureProtocol = true
            }
        }
        publications {
            javaMaven(MavenPublication) {
                artifactId = archName
                from components.java
            }
        }
    }

    // remove after https://youtrack.jetbrains.com/issue/IDEA-227215 is fixed
    tasks.withType(GenerateModuleMetadata) {
        enabled = false
    }
}

Hi,

Thanks a lot for reporting the problems.
We will fix this problem today.
You will be able to get a Studio with a fix in next nightly build or in release 2.4.0 build.

Regards,
Mikhail

1 Like

I noticed you have another nightly version available and i tried that one and getting the following error:

uild file '/Users/mak/Projects/inteaccHCM copy/inteaccfund/build.gradle' line: 1

A problem occurred evaluating project ':inteaccfund'.
> Could not find method implementation() for arguments [build_6mupyoerjuts6cyqfwm9559xy$_run_closure1@785eefa6] on configuration container of type org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

Hi,
Can you please attach your problem build.gradle file after and before migration process?
Also, if possible, attach the idea.log file.

Regards,
Mikhail

Since the log file size is large, I have send it by email to info at jmix.io

Hi,

I received the sent files, thank you very much.
The problem was localized - migration for addons was incorrect.

Regards,
Mikhail

1 Like

Hi Mikhail
Is that issue resolved?

Hi,

Yes, this issue has been fixed in 2.4.0 release version of Studio.
Are you still having problems with with migration?

Regards,
Mikhail

1 Like

Thanks and migration of my composite project worked.

1 Like