As stated by the changelog, the release of rest-assured v6 marked a major step forward, also in terms of major dependency version, creating a baseline for Spring Boot 4 (Jackson 3, Groovy 5, Java 17, etc.)
Yesterday one of our renovate pipelines suddenly failed, having a class not found exception in regards of Apache HttpComponents. It turned out to be the classical transitive dependency issue, we could fix that on our side, so this is not a bug report but a feature request.
Spring Boot 4 moves towards HttpComponents 5 supporting it as first class citicen.
Rest-Assured still uses v4, which in general is not a problem, also feature wise the bump might not be that urgent, yet in terms of dependency management, this is a thing. Currently, having rest-assured in your Spring Boot v4 project, you end up with both versions in the classpath. Luckily, the package structure was changed so you do not run into classpath issues.
Yet, it "feels" a bit wonky to have both versions on the classpath in a project that otherwise uses the latest and greatest dependency set.
The feature has been requested some years ago also (#1696) but I thought I'll raise a new one as of the latest development in the whole ecosystem and the new rest-assured v6 baseline. The other issue I think can be closed as being a duplicate of this one.
Thanks.
As stated by the changelog, the release of rest-assured v6 marked a major step forward, also in terms of major dependency version, creating a baseline for Spring Boot 4 (Jackson 3, Groovy 5, Java 17, etc.)
Yesterday one of our renovate pipelines suddenly failed, having a class not found exception in regards of Apache HttpComponents. It turned out to be the classical transitive dependency issue, we could fix that on our side, so this is not a bug report but a feature request.
Spring Boot 4 moves towards HttpComponents 5 supporting it as first class citicen.
Rest-Assured still uses v4, which in general is not a problem, also feature wise the bump might not be that urgent, yet in terms of dependency management, this is a thing. Currently, having rest-assured in your Spring Boot v4 project, you end up with both versions in the classpath. Luckily, the package structure was changed so you do not run into classpath issues.
Yet, it "feels" a bit wonky to have both versions on the classpath in a project that otherwise uses the latest and greatest dependency set.
The feature has been requested some years ago also (#1696) but I thought I'll raise a new one as of the latest development in the whole ecosystem and the new rest-assured v6 baseline. The other issue I think can be closed as being a duplicate of this one.
Thanks.