1

I am currently trying to update our Spring Boot Applications to Spring Boot 3.0.5. Accordingly I am trying to migrate to Spring Cloud GCP version 4.1.4, which according to their readme on github is intended to be compatible with Spring Boot 3.x.

However their Starter spring-cloud-gcp-starter-logging in version 4.1.4 depends on:

(Sorry Stackoverflow only lets me post up to 8 links appearantly, but you can access all these artifacts through the above link to google-cloud-logging-logback/0.130.9-alpha)

Now as to my understanding, as Spring Boot 3.x uses Java 17 all javax packages should be replaced by their jakarta alternatives, in this case javax.annotation-api should be replaced with jakarta.annotation-api (actually since Java 11 already right?)

Also to my understanding, the apache httpcomponents 4.x artifacts should be replaced with their apache httpcomponents.core5 and apache httpcomponents.client5 counterparts.

Is this a bug, or am I misunderstanding or missing something?

Alpengringo
  • 11
  • 1
  • The fact that Spring doesn't support HTTP client 4.x doesn't mean other libraries still cannot use that. So unless you are using it yourself there is nothing in there that is blatently wrong. I'm also not sure what the problem is you have? DOesn't it work? Does it break? – M. Deinum Apr 19 '23 at 13:47
  • Thank you @M.Deinum for your reply! No it does not break per say, but I keep having external libraries in my projects that are outdated. As part of the upgrade process I am looking through the external libraries of my projects and try to eleminate any outdated/deprecated dependencies. Having http components 4 and javax in my dependancy tree from this one dependancy when everything else uses 5 and jakarta just seems unclean/error prone to me. – Alpengringo Apr 19 '23 at 14:21
  • Well apparently Google Cloud needs that. As stated the fact that Spring doesn't use it doesn't mean others don't. – M. Deinum Apr 19 '23 at 17:39

0 Answers0