Currently we generate the JMS source artifacts based on the starter, but we do not include any JMS client libraries, nor do we set up any connection factories. Consequently, the JmsAutoConfiguration is not triggered, and the generated artifacts fail to start.
Copied from original issue: spring-cloud/spring-cloud-stream-app-starters#135
From @mbogoevici on June 15, 2016 14:52
Currently we generate the JMS source artifacts based on the starter, but we do not include any JMS client libraries, nor do we set up any connection factories. Consequently, the
JmsAutoConfiguration
is not triggered, and the generated artifacts fail to start.Copied from original issue: spring-cloud/spring-cloud-stream-app-starters#135