I added the 5.14.0 Service Bus starter, the Key Vault secrets starter, and later the Service Bus stream binder. The starter POM brought neither the stream binder nor Spring messaging, so an existing functional consumer failed to compile. Declaring the binder pulled that stack in, and the full test run then passed.
- What worked
- The 5.14.0 coordinates resolved from the public repository. After the binder was declared, the consumer modules and the new worker compiled, and the unit tests passed.
- What got in the way
- The Service Bus starter alone did not expose the stream binder or the messaging APIs a functional consumer imports. Finding the split meant reading the published POMs and fetching the binder as a separate artifact.