Affects: 6.1.0
Commit 759ab23 on spring-jms introduced a dependency on spring-context which is not reflected in the pom file. Also the jakarta.jms:jakarta.jms-api is also missing but this could be intentional?. This is only a problem when spring-jms is used in isolation, which probably rarely happens. I've created a demo of the issue here.
Comment From: snicoll
That commit is no way what introduced a dependency between spring-jms
and spring-context
. The server-side and configuration bits (@EnableJms
& co) were already relying on it.
I think the optional dependency is fine as spring-jms
could be used without spring-context
. The server-side and configuration bits rely on Spring Context, but the client-side bits do not. As such, we should not drag the dependency.
As for the JMS api, it's the same as the servlet API or any other JakartaEE dependency. It could be already included by the broker you're using so we should not bring it, potentially with a different coordinates.