TransactionEssentials 6.0.0 is broken with Spring Boot 3.4.0

[ibmmqmet]

A JMS program that worked with Spring Boot 3.3.6 is broken with 3.4.0 because of it calling a missing method.

Looks to be the same thing that caused snowdrop/narayana-spring-boot#172

APPLICATION FAILED TO START


Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    com.atomikos.spring.AtomikosAutoConfiguration.lambda$transactionManager$0(AtomikosAutoConfiguration.java:84)

The following method did not exist:

    'void org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers.customize(org.springframework.transaction.PlatformTransaction
Manager)'

The calling method's class, com.atomikos.spring.AtomikosAutoConfiguration, was loaded from the following location:

    jar:file:/home/metaylor/.gradle/caches/modules-2/files-2.1/com.atomikos/transactions-spring-boot3/6.0.0/d469a4ebaa9a86e0e979dfafd82ecd2bb655e255/tra
nsactions-spring-boot3-6.0.0.jar!/com/atomikos/spring/AtomikosAutoConfiguration.class

The called method's class, org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers, is available from the following locations:

    jar:file:/home/metaylor/.gradle/caches/modules-2/files-2.1/org.springframework.boot/spring-boot-autoconfigure/3.4.0/2cf78b01be25952c96cb8ee60b4b0562
b3a136f2/spring-boot-autoconfigure-3.4.0.jar!/org/springframework/boot/autoconfigure/transaction/TransactionManagerCustomizers.class

The called method's class hierarchy was loaded from the following locations:

    org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers: file:/home/metaylor/.gradle/caches/modules-2/files-2.1/org.springf
ramework.boot/spring-boot-autoconfigure/3.4.0/2cf78b01be25952c96cb8ee60b4b0562b3a136f2/spring-boot-autoconfigure-3.4.0.jar

[ibmmqmet]

Changing boot.version in transactions-essentials/public/spring-boot3/pom.xml from 3.0.1 to 3.4.0 and rebuilding from that directory "solves" the problem. But obviously that's not the right thing to do as it forces the version change.

[thijmenketel]

I guess an update is not likely as the last PR merge was in march :(