Closed ideas-into-software closed 1 year ago
Possibly a separate branch, jakarta-servlet-5-x
could be maintained, instead of merging to master?
Is there any interesst in merging this, as we would highly appreciate this change as well.
@ideas-into-software We created the jakarta5
branch. ~Can you resolve the conflicts and point the PR to the jakarta5
branch?~ and it contains this change and we will make a release soon :rocket:
@oliemansm you can close this PR
Closing this as @federicorispo added this to https://github.com/graphql-java-kickstart/graphql-java-servlet/tree/jakarta5 branch via https://github.com/graphql-java-kickstart/graphql-java-servlet/commit/72fba8be2cb945eb38303efbfd1fa7c9ff996972 commit
As per Federico Rispo's comment Federico Rispo's comment (https://github.com/graphql-java-kickstart/graphql-java-servlet/discussions/508#discussioncomment-5276382),
GraphQL Java Servlet
is dependent onJakarta Servlet 6.x
only because ofSpring
dependencies, which are only used for testing. Therefore, it was possible to relaxJakarta Servlet API
version to5.x
, while keepingJakarta Servlet API
version at6.x
for 'testImplementation' dependencies.Most of our projects use
Apache Felix Jetty
and requiringJakarta Servlet 6.x
made it impossible to use that container.Thanks to this small change,
GraphQL Java Servlet
is now compatible with latest version ofApache Felix Jetty
, as well as many other servlet containers which do not yet supportJakarta Servlet 6.x
.