Upgrade baseline to Java 17 and Jakarta APIs

[bclozel]

Spring for GraphQL 1.1.0 will be released for Spring Boot 3.0 and Spring Framework 6.0.
As previously announced, this raises the baseline to Java 17 and Jakarta EE 9 APIs.

[andrei-ivanov]

Wouldn't it be better to increase the major version for such changes?

[bclozel]

Yes, this has been discussed a lot within the Spring for GraphQL team. A new major version would be indeed in line with the Spring team's policy.

But given the recent 1.0 release and the upcoming Spring Framework 6.0 and Spring Boot 3.0 releases, we were left with 3 choices:

1. Cut a new 2.0 release only a few months after the 1.0, leaving us no room for important changes in the next years. At this point, the community is starting to adopt this project and we're collecting more and more feedback.
2. Not release a Spring for GraphQL version compatible with Spring Boot 3.0 right away and waiting a few months until we feel ready to have a new major version. This would effectively leave a "support gap" for Spring Boot 2.7 users willing to upgrade to Spring Boot 3.0. Community was already asking for Spring Boot 3.0 plans.
3. Cut a 1.1.0 release, just adapting to baseline requirements and not breaking APIs. We can then consider releasing a more ambitious 2.0 version during the lifetime of the Spring Boot 3.x generation, always balancing the upgrade experience with changes requested by the community

After discussing this matter with the Spring Framework and Spring Boot team, we chose 3).

[bclozel]

This has been updated in 1.1.0 as a result of spring-projects/spring-framework#29435