Mention code namespace changes in migration guide

[ibmmqmet]

I'm trying to rebuild my MQ JMS Boot Starter against the M1 snapshot, and getting missing packages/classes. I switched to

api group: 'org.springframework.boot', name: 'spring-boot-starter-jms', version: springBootVersion
api group: 'org.springframework.boot', name: 'spring-boot-tx', version: springBootVersion

in my gradle config that works fine for Boot3 . But I'm getting lots of errors like:

mq-boot4-spring-boot-starter/src/main/java/com/ibm/mq/spring/boot/MQConfigurationListenerDefault.java:23: error: package org.springframework.boot.autoconfigure.jms does not exist
import org.springframework.boot.autoconfigure.jms.JmsProperties;

mq-boot4-spring-boot-starter/src/main/java/com/ibm/mq/spring/boot/MQAutoConfiguration.java:24: error: package org.springframework.boot.autoconfigure.jms does not exist
import org.springframework.boot.autoconfigure.jms.JmsAutoConfiguration;

And similar for JtaAutoConfiguration.

I know the new jar files are being downloaded, along with their dependencies, and I can see the classes inside those jars. ONE class from them (XAConnectionFactoryWrapper) appears to be recognised during the build. But it's just about everything else that's not found.

I've tried everything I can think of, including using "bad" artifact names to prove that the lines in the build.gradle are being processed.

Are there extra jars neeed? Anything different needed for the build against Boot4?

[bclozel]

You will need to change imports as modularization efforts also involved package name changes. For example what you are looking for lives in "org.springframework.boot.jms.autoconfigure" now.

[ibmmqmet]

a) that doesn't seem to be mentioned in the migration guide - is it written somewhere else?
b) it makes it harder to have the same code for both boot3 and boot4

[bclozel]

a) thanks for raising this. We will use this issue to update the guide.

b) this is indeed a major change, well suited for a major version. We expect starters to release new major versions as well and introduce their own breaking changes if needed.