Jmix 1.6 BootBuildImage error (@Input annotation)

Support
#1

Dear Jmix team,

I’m trying to do ./gradlew bootBuildImage but unfortunattely build fails with the @Input annotation error. See below. Problem can be reproduced on new blank Jmix 1.6 project.

Could you please give me some advice?

Thank you.
OG

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':bootBuildImage' (type 'BootBuildImage').
  - In plugin 'org.springframework.boot' type 'org.springframework.boot.gradle.tasks.bundling.BootBuildImage' property 'archiveFile' has @Input annotation used on property of type 'RegularFileProperty'.
    
    Reason: A property of type 'RegularFileProperty' annotated with @Input cannot determine how to interpret the file.
    
    Possible solutions:
      1. Annotate with @InputFile for regular files.
      2. Annotate with @InputFiles for collections of files.
      3. If you want to track the path, return File.absolutePath as a String and keep @Input.
    
    Please refer to https://docs.gradle.org/8.0.2/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.
#2

I was able to solve this by setting the springboot gradle plugin version explicitly.

Without any configuration gradle used SpringBootPlugin version 2.7.4. I used settings in build.gradle like the snippet below to enforce 2.7.18 plugin version. I’m I missing something or explicit SpringBootPlugin version must be part of build.gradle configuration?

Thanks.

OG

buildscript {
    ext {
        springBootVersion = '2.7.18'
    }
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath(
                "org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
    }
}
#4

Hello

For now Jmix uses 2.7.4 plugin version, thank you for reporting it! The issue to update this version has been created.

Yes, currently a newer version have to be enforced in order to use features from it.

Regards,
Dmitry

#6

Thanks Dmitry for your response.