Edit by Adrien: Since the question was posted without a body, I took the liberty of filling in the symptoms.
If a plugin needs a cache, the Atlassian documentation advises to import following, which doesn't work:
<component-import key="cacheFactory" interface="com.atlassian.cache.CacheFactory" />
The plugin installation fails with the following messages:
Plugin 'com.[...]' never resolved service '&cacheFactory' with filter '(objectClass=com.atlassian.cache.CacheFactory)'
How to use the cache in JIRA?
As Nic said, you haven't given us much to work with, but I'll take a wild stab...
For historic reasons, JIRA exports the heavier CacheManager interface instead of the nice, thin CacheFactory. It really shouldn't do this, because CacheManager has management interfaces that plugins have no business using, like flushing all of the caches, but it's what we did so it's here to stay for the time being.
This may make it harder for the plugin system to resolve it as a CacheFactory, particularly if you are using the atlassian-cache-compat for cross-version compatibility or have made your plugin "transformerless".
@Adrien Ragot (Play SQL / CYO): "... the Atlassian documentation advises ..."
Could you provide a link to the documentation that you're speaking of? The only example of that I have been able to find was in the documentation for Stash add-on developers, and it actually works there because they were not burdened with this historical usage and chose to register it in the container properly.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs