Caches defined in configuration are no longer available on startup

[snicoll]

I am trying to migrate to ehcache 3.11.0 in Spring Boot (from 3.10.8). We have a test with the following configuration:

<config
		xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
		xmlns='http://www.ehcache.org/v3'
		xmlns:jsr107='http://www.ehcache.org/v3/jsr107'
		xsi:schemaLocation="
		http://www.ehcache.org/v3 https://www.ehcache.org/schema/ehcache-core-3.10.xsd
		http://www.ehcache.org/v3/jsr107 https://www.ehcache.org/schema/ehcache-107-ext-3.10.xsd">

	<cache-template name="example">
		<heap unit="entries">200</heap>
	</cache-template>

	<cache alias="foo" uses-template="example">
		<expiry>
			<ttl unit="seconds">600</ttl>
		</expiry>
		<jsr107:mbeans enable-statistics="true"/>
	</cache>

	<cache alias="bar" uses-template="example">
		<expiry>
			<ttl unit="seconds">400</ttl>
		</expiry>
	</cache>

</config>

Thus far, this means that, on startup, Eh107CacheManager loaded with this configuration exposes two caches, i.e. cacheManager#getCacheNames() returns foo and bar.

Upgrading to 3.11.0, it returns an empty list. I can see that the underlying org.ehcache.CacheManager still has the two caches loaded in its caches map field, so it must be something that has changed in between.

Is this change intended? If so, where can I learn about it?

[chrisdennis]

Sorry... paperwork including release notes etc is on my list to get out this week. That said this wasn't intended, I'll dig in and see what I can find.

[chrisdennis]

Fixed with #3274. I validated the spring-boot tests locally and everything seems to be good now. Apologies for the bad release. I'm cutting 3.11.1 right now so I expect dependabot and its ilk to pick it up imminently. Website, documentation and release notes should get done later this afternoon if nothing else goes wrong 🤞