close

Filter

loading table of contents...

Release Notes / Version 11.2310

Table Of Contents

Changed @BeansForPlugins Dependency Policy

While in theory it was recommended to provide @BeansForPlugins classes in separate artifacts, on which plugins should depend with scope compile, reality looks different, and most @BeansForPlugins artifacts must be used with scope provided. Therefore we also moved CommonBeansForPluginsConfiguration and CommerceBeansForPluginsConfiguration to provided artifacts.

The exact new locations and dependencies can be taken from the Blueprint Developer Manual, section "Application Beans in Plugins". The old classes are deprecated but will remain in place, so there is no need to change existing plugins.

(CMS-23466)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.