Skip to content

Spring-boot 3.1.2 version can be built successfully, but higher versions cannot! #46469

@elf-world

Description

@elf-world

Building with Spring-boot 3.5.3 failed, here are the logs

PS H:\Auto-play> ./gradlew.bat :server:clean :server:build                                                                                                                                                                               
> Task :server:bootJar FAILED                                                                                                                                                                                                            

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':server:bootJar'.
> 'void org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.zip.ZipArchiveEntry)'

* 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.

BUILD FAILED in 4s
5 actionable tasks: 5 executed

The build was successful using Spring-boot 3.1.2. Here are the logs:

PS H:\Auto-play> ./gradlew.bat :server:clean :server:build                                                                                                                                                                               

[Incubating] Problems report is available at: file:///H:/Auto-play/build/reports/problems/problems-report.html
                                                                                                                                                                                                                                         
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.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 1s
6 actionable tasks: 5 executed, 1 from cache
PS H:\Auto-play>  

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions